You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to setup jorani with authentik as SAML provider.
However, i always get the following result when accessing jorani (via the jorani-base-url) and am unable to get past it:
The behaviour is different, when opening jorani from within authentik - then it submits a POST request to jorani, but stops at https://<jorani-base-url>/api/acs and displays a blank page.
Is jorani possibly incompatible with authentik?
The authentik version is 2023.5.
What is the version of Jorani?
1.0.2
Expected behavior
The login procedure via SAML works.
Actual behavior
Login does not work, i always end up with authentik complaining The SAML request payload is missing..
Behind the scenes the login-functions themselves seem to do something, as the amount of successful Authorizations increases each time (seen in authentik).
Steps to reproduce the behavior
Setup jorani in authentik (set ACS URL, Issuer URL, Service Provider Binding to POST, set Signing Certificate, set no Verification Certificate)
Setup saml in jorani (entityId, signon/signout urls and certificate as provided by authentik)
The text was updated successfully, but these errors were encountered:
Never heard of Authentik. I've tested with Auth0, Azure, Google, and AWS. SAML is a standard so it should work everywhere.
You should check the logs on both sides.
I tried to setup jorani with authentik as SAML provider.
However, i always get the following result when accessing jorani (via the jorani-base-url) and am unable to get past it:
The behaviour is different, when opening jorani from within authentik - then it submits a POST request to jorani, but stops at
https://<jorani-base-url>/api/acs
and displays a blank page.Is jorani possibly incompatible with authentik?
The authentik version is
2023.5
.What is the version of Jorani?
1.0.2
Expected behavior
The login procedure via SAML works.
Actual behavior
Login does not work, i always end up with authentik complaining
The SAML request payload is missing.
.Behind the scenes the login-functions themselves seem to do something, as the amount of successful Authorizations increases each time (seen in authentik).
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: