Skip to content

Fix HostAuthenticationStateProvider to use relative return URLs#387

Merged
kevinchalet merged 1 commit intoopeniddict:devfrom
kevinchalet:return_url
Feb 28, 2026
Merged

Fix HostAuthenticationStateProvider to use relative return URLs#387
kevinchalet merged 1 commit intoopeniddict:devfrom
kevinchalet:return_url

Conversation

@kevinchalet
Copy link
Copy Markdown
Member

Fixes #382.

@kevinchalet kevinchalet self-assigned this Feb 28, 2026
@kevinchalet kevinchalet merged commit 710b112 into openiddict:dev Feb 28, 2026
3 checks passed
@kevinchalet kevinchalet deleted the return_url branch February 28, 2026 14:57
@JJong-nl
Copy link
Copy Markdown

ps : one small naming.
For prerender/server render blazor is using the normal ServerAuthenticationStateProvider as it should.
And rendermodes can be set to Server of webassembly.
Instead the HostAuthenticationStateProvider maybe namechange to WasmAuthenticationStateProvider?

@JJong-nl
Copy link
Copy Markdown

Than for the httpclients that using yarp forwarding. In wasm the cookie is coppied by the baseaddress. But when using server prerender a httpclient that should call the yarp forwarding should need the current cookie added to the server request. Can be done by request options and httpmessage middleware.

If you would like, i could sens sample

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Resturn url should always be relative

2 participants