Stefan Benz 0e10ed0e0b

fix: SAML and OIDC issuer (in proxied use cases) (#9638) ...

# Which Problems Are Solved

When using implicit flow through the session API and a login UI on a
custom domain (proxy), the tokens were signed by the API domain of the
instance, rather than the public (proxy) domain.
The SAML response had the same issue. Additionally, the saml library had
an issue and lost the issuer context. This prevented also a successful
login through the hosted login UI.

# How the Problems Are Solved

- The issuer of the SAML and Auth request is persisted to provide the
information when signing the responses and tokens.
- The SAML library is updated to the latest version.

# Additional Changes

None

# Additional Context

None

2025-03-26 17:08:13 +00:00

..

integration

feat: permission check on OIDC and SAML service session API (#9304)

2025-02-11 18:45:09 +00:00

saml.go

fix: SAML and OIDC issuer (in proxied use cases) (#9638)

2025-03-26 17:08:13 +00:00

server.go

feat: add saml request to link to sessions (#9001)

2024-12-19 11:11:40 +00:00