Open Meteoeoeo opened 1 year ago
Did you debug the custom config in your http example to hold the correct values?
@Meteoeoeo did you get around fixing this please?
Hi, I changed a few things, I don't remember what exactly helped, because it was some time ago. It seems to me that the first point solved the above problem, but I will describe you what else I changed.
window.location.href
to the checkAuth
method, the earlier version didn't need it and it wasn't described in the migration steps.this._oidcSecurityService.checkAuth(window.location.href)
{ path: '**', redirectTo: '/home' }
CanActivateFn
export const AuthGuard: CanActivateFn = (
_route: ActivatedRouteSnapshot,
_state: RouterStateSnapshot) => {
const _authService = inject(AuthenticationService);
[...]
}
Did you debug the custom config in your http example to hold the correct values?
while debugging, I had the correct values in the configuration, but the checkAuth method was not returning the token
Thank you @Meteoeoeo
Could you solve this?
Greetings Damien
Having this same issue using code flow. When we moved from using hard coded config to loading the config via http, login would no longer work (checkAuth showed isAuthenticated: false, after redirecting from SSO back to app) solution 1. added window.location.href to the checkAuth method fixed this for us but no idea why.
Version
15.0.3
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Steps to reproduce the behavior
No response
A clear and concise description of what you expected to happen.
No response
Additional context
After migration to v15 from v12 i have problem with getting configuration. Configuration inside checkauth is downloaded from service, but token is null and isAuthenticated is false. In the response from identity server token exists.
When I change configuration to static it's work correctly.