Angular2: Login with api fails to get data sometimes
0
I'm trying to login on web with authentication of token got from Web-API. I am saving the token in cookies and proceed my work.
I want to ask that if i am login with admin on one tab and without logout, i will login again.
Then, sometimes the result would not get as expected (data i got sometimes was incomplete).
Is this the issue of cookies ? Is it remembering the previous token that i have not cleared on previous tab login page. What should i do to fix this issue?
Please check the below code of login
Login(model: LoginViewModel): Observable<any>
// let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password" + "&client_id=" + "&client_secret=";
let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password";
let url = APIURL + "/token";
return this._http.post(url, body, AuthService.OptionsUrlEncoded)
.map(response =>
this.AddClaims(response.json())
this.ExpireTime();
)
.catch(this.HandleError);
angular asp.net-web-api session-cookies angular-cookies
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
add a comment |
0
I'm trying to login on web with authentication of token got from Web-API. I am saving the token in cookies and proceed my work.
I want to ask that if i am login with admin on one tab and without logout, i will login again.
Then, sometimes the result would not get as expected (data i got sometimes was incomplete).
Is this the issue of cookies ? Is it remembering the previous token that i have not cleared on previous tab login page. What should i do to fix this issue?
Please check the below code of login
Login(model: LoginViewModel): Observable<any>
// let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password" + "&client_id=" + "&client_secret=";
let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password";
let url = APIURL + "/token";
return this._http.post(url, body, AuthService.OptionsUrlEncoded)
.map(response =>
this.AddClaims(response.json())
this.ExpireTime();
)
.catch(this.HandleError);
angular asp.net-web-api session-cookies angular-cookies
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
Please describe more precisely what is the behaviour you are witnessing. I don't quite understand your description. Then people can better help :)
– Mic
Nov 15 '18 at 8:36
My login function is authenticating and getting token from asp.net Web api. and then save that token in application cookies. I'm having trouble in getting data by using this token on new login tab. Suppose user A is login on a windows tab. He doesn't logout. Then opens the new windows tab and login again. This time, the data will be inappropriate sometimes
– Manisha Jain
Nov 15 '18 at 8:42
You should try to better caracterize the "sometimes". Withconsole.logcalls, try to pinpoint the conditions when it fails.
– Mic
Nov 15 '18 at 9:09
Actually that "sometimes" happens in a while. I faced it once last month. So, its really tough for me to configure it by console.log calls. I just don't want to get that type of issue again. I think it may be the issue of token mismatch. Can't say clearly without having the failure case. If anything can be done, please suggest.
– Manisha Jain
Nov 15 '18 at 9:44
Do your tokens have an expiration time? Maybe they just expire after a while and you need to refresh them in case they do.
– Mic
Nov 15 '18 at 13:54
add a comment |
0
0
0
I'm trying to login on web with authentication of token got from Web-API. I am saving the token in cookies and proceed my work.
I want to ask that if i am login with admin on one tab and without logout, i will login again.
Then, sometimes the result would not get as expected (data i got sometimes was incomplete).
Is this the issue of cookies ? Is it remembering the previous token that i have not cleared on previous tab login page. What should i do to fix this issue?
Please check the below code of login
Login(model: LoginViewModel): Observable<any>
// let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password" + "&client_id=" + "&client_secret=";
let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password";
let url = APIURL + "/token";
return this._http.post(url, body, AuthService.OptionsUrlEncoded)
.map(response =>
this.AddClaims(response.json())
this.ExpireTime();
)
.catch(this.HandleError);
angular asp.net-web-api session-cookies angular-cookies
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
I'm trying to login on web with authentication of token got from Web-API. I am saving the token in cookies and proceed my work.
I want to ask that if i am login with admin on one tab and without logout, i will login again.
Then, sometimes the result would not get as expected (data i got sometimes was incomplete).
Is this the issue of cookies ? Is it remembering the previous token that i have not cleared on previous tab login page. What should i do to fix this issue?
Please check the below code of login
Login(model: LoginViewModel): Observable<any>
// let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password" + "&client_id=" + "&client_secret=";
let body = "username=" + model.UserName + "&password=" + model.Password + "&grant_type=password";
let url = APIURL + "/token";
return this._http.post(url, body, AuthService.OptionsUrlEncoded)
.map(response =>
this.AddClaims(response.json())
this.ExpireTime();
)
.catch(this.HandleError);
angular asp.net-web-api session-cookies angular-cookies
angular asp.net-web-api session-cookies angular-cookies
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
edited Nov 15 '18 at 8:33
Manisha Jain
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
asked Nov 15 '18 at 8:31
Manisha JainManisha Jain
11
11
Please describe more precisely what is the behaviour you are witnessing. I don't quite understand your description. Then people can better help :)
– Mic
Nov 15 '18 at 8:36
My login function is authenticating and getting token from asp.net Web api. and then save that token in application cookies. I'm having trouble in getting data by using this token on new login tab. Suppose user A is login on a windows tab. He doesn't logout. Then opens the new windows tab and login again. This time, the data will be inappropriate sometimes
– Manisha Jain
Nov 15 '18 at 8:42
You should try to better caracterize the "sometimes". Withconsole.logcalls, try to pinpoint the conditions when it fails.
– Mic
Nov 15 '18 at 9:09
Actually that "sometimes" happens in a while. I faced it once last month. So, its really tough for me to configure it by console.log calls. I just don't want to get that type of issue again. I think it may be the issue of token mismatch. Can't say clearly without having the failure case. If anything can be done, please suggest.
– Manisha Jain
Nov 15 '18 at 9:44
Do your tokens have an expiration time? Maybe they just expire after a while and you need to refresh them in case they do.
– Mic
Nov 15 '18 at 13:54
add a comment |
Please describe more precisely what is the behaviour you are witnessing. I don't quite understand your description. Then people can better help :)
– Mic
Nov 15 '18 at 8:36
My login function is authenticating and getting token from asp.net Web api. and then save that token in application cookies. I'm having trouble in getting data by using this token on new login tab. Suppose user A is login on a windows tab. He doesn't logout. Then opens the new windows tab and login again. This time, the data will be inappropriate sometimes
– Manisha Jain
Nov 15 '18 at 8:42
You should try to better caracterize the "sometimes". Withconsole.logcalls, try to pinpoint the conditions when it fails.
– Mic
Nov 15 '18 at 9:09
Actually that "sometimes" happens in a while. I faced it once last month. So, its really tough for me to configure it by console.log calls. I just don't want to get that type of issue again. I think it may be the issue of token mismatch. Can't say clearly without having the failure case. If anything can be done, please suggest.
– Manisha Jain
Nov 15 '18 at 9:44
Do your tokens have an expiration time? Maybe they just expire after a while and you need to refresh them in case they do.
– Mic
Nov 15 '18 at 13:54
Please describe more precisely what is the behaviour you are witnessing. I don't quite understand your description. Then people can better help :)
– Mic
Nov 15 '18 at 8:36
Please describe more precisely what is the behaviour you are witnessing. I don't quite understand your description. Then people can better help :)
– Mic
Nov 15 '18 at 8:36
My login function is authenticating and getting token from asp.net Web api. and then save that token in application cookies. I'm having trouble in getting data by using this token on new login tab. Suppose user A is login on a windows tab. He doesn't logout. Then opens the new windows tab and login again. This time, the data will be inappropriate sometimes
– Manisha Jain
Nov 15 '18 at 8:42
My login function is authenticating and getting token from asp.net Web api. and then save that token in application cookies. I'm having trouble in getting data by using this token on new login tab. Suppose user A is login on a windows tab. He doesn't logout. Then opens the new windows tab and login again. This time, the data will be inappropriate sometimes
– Manisha Jain
Nov 15 '18 at 8:42
You should try to better caracterize the "sometimes". With
console.log calls, try to pinpoint the conditions when it fails.– Mic
Nov 15 '18 at 9:09
You should try to better caracterize the "sometimes". With
console.log calls, try to pinpoint the conditions when it fails.– Mic
Nov 15 '18 at 9:09
Actually that "sometimes" happens in a while. I faced it once last month. So, its really tough for me to configure it by console.log calls. I just don't want to get that type of issue again. I think it may be the issue of token mismatch. Can't say clearly without having the failure case. If anything can be done, please suggest.
– Manisha Jain
Nov 15 '18 at 9:44
Actually that "sometimes" happens in a while. I faced it once last month. So, its really tough for me to configure it by console.log calls. I just don't want to get that type of issue again. I think it may be the issue of token mismatch. Can't say clearly without having the failure case. If anything can be done, please suggest.
– Manisha Jain
Nov 15 '18 at 9:44
Do your tokens have an expiration time? Maybe they just expire after a while and you need to refresh them in case they do.
– Mic
Nov 15 '18 at 13:54
Do your tokens have an expiration time? Maybe they just expire after a while and you need to refresh them in case they do.
– Mic
Nov 15 '18 at 13:54
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53315207%2fangular2-login-with-api-fails-to-get-data-sometimes%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53315207%2fangular2-login-with-api-fails-to-get-data-sometimes%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please describe more precisely what is the behaviour you are witnessing. I don't quite understand your description. Then people can better help :)
– Mic
Nov 15 '18 at 8:36
My login function is authenticating and getting token from asp.net Web api. and then save that token in application cookies. I'm having trouble in getting data by using this token on new login tab. Suppose user A is login on a windows tab. He doesn't logout. Then opens the new windows tab and login again. This time, the data will be inappropriate sometimes
– Manisha Jain
Nov 15 '18 at 8:42
You should try to better caracterize the "sometimes". With
console.logcalls, try to pinpoint the conditions when it fails.– Mic
Nov 15 '18 at 9:09
Actually that "sometimes" happens in a while. I faced it once last month. So, its really tough for me to configure it by console.log calls. I just don't want to get that type of issue again. I think it may be the issue of token mismatch. Can't say clearly without having the failure case. If anything can be done, please suggest.
– Manisha Jain
Nov 15 '18 at 9:44
Do your tokens have an expiration time? Maybe they just expire after a while and you need to refresh them in case they do.
– Mic
Nov 15 '18 at 13:54