deep links

[hneemann]

Is there a simple example of how to pass a deep link through the login process so that you can redirect to it after logging in?

[muhlemmer]

No we do not have an example, but one could use the state parameter to do such things.

[hneemann]

This is difficult because the stateFn function has no arguments. If it had the *http.Request as an argument, you could access the request and use the deep link to generate the state string.

[muhlemmer]

That's for the secure state cookie.

I was talking about the state request field in the Auth Request. You can set that to any string. So one could create a State struct type, add relevant state that needs to be kept until redirect back to the app (like deep links). The struct can be marshalled, encoded or however you want to make that a string. Once the authorization flow is completed, your receive the state string back as part of the AccessTokenResponse. Decode it and voila.

[hneemann]

Hmm! I stumbled across this example, and it seems to be explained differently there.
Isn't the state simply set as a parameter in the URL of the redirect to the OIDC server? That seems to be done without using the AuthRequest struct at all.

[muhlemmer]

That example creates a simple string to populate the request field, but the comment explains exactly what your want to achieve:

oidc/example/client/app/app.go

Line 89 in e4fc8af

// e.g. the page where he was before sending him to login

Deep link is exactly that. My example was a bit expanded in case people need to append more data to the state param.

[hneemann]

However, at the time this function is declared, the request is not yet known, and when the function is called, it does not have access to the request. How can the deep link be extracted from the request?
It would not be a problem if the function had the signature “func(*http.Request) string.”