authorize-path and clarity

[ArsLucidum]

I've had some problems making the directive work with google. It took me a while to figure out that the cause was not using the authorize-path attribute in my directive, as it was defaulting to "/oauth/authorize" and appending that to my url, thus sending me to the wrong page.

For clarity, I think it would be better to either have it default to nothing at all, or making it more clear in the documentation that this might be a common issue.

[m00s]

Hi @kace91, seems like no one else has had the same issue.

IMO /oauth/authorize is widely used as authorization endpoint so I think we'll keep it as default value. Do you have any suggestion to make it more clear in the documentation?

[boldt]

I had the same issue with a Keycloak server. Took me quite a while, to figure out this issse, e.g, that /oauth/authorize was added to the URL.