You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to integrate oauth-ng in my application by setting up manual configuration. we observe following issues.
When it set request type 'token id_token' application blindly showing access denied link even my provider returns everything.
When we set log-out URL the oauth-ng JS file initView checking for AccessToken when it is null it is calling for logout method. and this process repeating infinitely.
When I check oauth-ng.js initView function it is expecting token to be available on initial page load only. if token not available then it calling logout.
I put <oauth tag on landing page itself because of that initView calling on page loading and it calling infinitely logout URL.
The text was updated successfully, but these errors were encountered:
I worked that around not using the directive's setting but rather implementing the logout event and doing the redirection myself. $rootScope.$on('oauth:logout', function() { if(!($rootScope.accessToken === null || $rootScope.accessToken === undefined)){//otherwise infinite redirect loop $rootScope.accessToken = null; var tempIdToken = $rootScope.idToken; $rootScope.idToken = null; var redirectLink = URLTOENDSESSIONENDPOINT+ '?post_logout_redirect_uri=' + POSTLOGOUTURL + '&id_token_hint=' + tempIdToken; $window.open(redirectLink, '_self'); } });
I am trying to integrate oauth-ng in my application by setting up manual configuration. we observe following issues.
When I check oauth-ng.js initView function it is expecting token to be available on initial page load only. if token not available then it calling logout.
I put <oauth tag on landing page itself because of that initView calling on page loading and it calling infinitely logout URL.
The text was updated successfully, but these errors were encountered: