Callback URL not approved for this client application about web-auth

[thekid]

Doesn't occur with GitHub, which seems to have a more relaxed (and intuitive) understanding of callback URL matching.

[thekid]

Microsoft Office 365 OAuth has the same restriction on paths - documented here: https://docs.microsoft.com/en-us/azure/active-directory/develop/reply-url - but is even stricter and doesn't allow request parameters.

[thekid]

The "relaxed" way doesn't seem the intended way, though. The documentation states:

Often times a developer will think that they need to be able to use a different redirect URL on each authorization request, and will try to change the query string parameters per request. This is not the intended use of the redirect URL, and should not be allowed by the authorization server. The server should reject any authorization requests with redirect URLs that are not an exact match of a registered URL.

...and concludes:

If a client wishes to include request-specific data in the redirect URL, it can instead use the “state” parameter to store data that will be included after the user is redirected. It can either encode the data in the state parameter itself, or use the state parameter as a session ID to store the state on the server.

We should store request parameters in the session and pass them behind rather than appending them to the redirect_url field; this will work in any case.

[thekid]

Fixed in https://github.com/xp-forge/web-auth/releases/tag/v2.1.0