onload: 'check-sso' not working without excludedUrls about keycloak-angular HOT 4 CLOSED

Hi @velorium-star,

Great that you are trying the library! So straight to the answers 😄 :

• Do you have any idea what could be the cause? Why is it necessary to give bearerExcludedUrls to avoid being redirected immediately to the keycloak?

Every time the bearer is added to the http request, the flow updates the token in order to refresh it. When updating, it will check if you are logged in and will redirect the user to the login page, because you are not logged in yet.

If a path is included in the bearerExcludedUrls, if the given url matches it, the token will not be refreshed because the interceptor will terminate the add bearer to header flow before and continue the request.

In your case, you added path / . Every url has / so all paths were excluded.
So try these options:

1. Use a different path for this page and add it to the bearerExcludedUrls. For example: main or another path.
2. The second option is to not use the keycloak-angular interceptor and add the bearer to your requests. In this case you could still use the / , but in every request you have to call the keycloak-angular method: KeycloakService#addTokenToHeader(headersArg?: HttpHeaders)

Thanks

from keycloak-angular.

@mauriciovigolo thanks for quick response.

OK, now it's clear. The only thing that bothers me is that url matching. If I understood you correctly if I exclude for example '/page' it will match '/page' but '/page/one' and '/page/one/two' also?

from keycloak-angular.

@velorium-star, as it is a regex, you may append $ to the end of your text, for example: /page$. In this example it will only match the url that finishes with '/page'.

from keycloak-angular.

@mauriciovigolo Perfect. I went through the code in the meanwhile. Everything is clear now. Thanks!

from keycloak-angular.