Closed linsolas closed 8 years ago
Hi, the best thing to do here (if you can) is to switch to Angular HTML5 routing mode. That will remove the need for a fragment and the URI will become http://my-server/silent-renew.
There's a good explanation of the different Angular modes on Stack Overflow:
I find that clearer than Angular's actual documentation.
I think that should sort that out for you so I'll close the issue but if you continue to have any problems just reopen it and let me know how I can help further.
Hello,
Thanks for the Silent Token Renewal feature, which is really useful for us. However, I have a question about its implementation. As far as I understand this feature, I have to provide an URI which looks like
http://my-server/#/silent-renew
. However, if I look on the RFC 6749 (The OAuth 2.0 Authorization Framework), it says that the endpoint URI should not include fragment:On our context, we use ForgeRock solution that does not allow fragments in the
redirect_uri
, which prevents the silent token renewal to work correctly.So did I missed something here? If not, how to accomodate the
silent-renew
feature with such constraints?Thanks