Hi, I have a taiga server installed using source code. I managed to get the saml-auth-contrib plugin to work for okta. So when i press “sign in with saml”, i get redirected to our okta sign in. i get authenticated fine (we’re seeing okta authentication successful). but when it return to my taiga URL, it shows 405 not allowed error
First of all, we do not use that plugin, so we probably won’t be of much help. You may try to contact the plugin author on Github, but seeing how long it has not been updated, maybe that won’t be of help either.
However, the issue is that you are trying to make a POST request to the discover page, which does not support the POST method. We do not have a Single Logout URL, so as per the Okta documentation, you should probably use the main SP URL.
For some reason I got this working or at least errors on the plugin are gone. but now im facing an issue on the account creation. Is taiga made to manually create the account and not based on other authentication methods? Taiga server config seems fine. Okta authentication is succesful and redirects normally. but then taiga server doesn’t recognize the credentials/account.
I’m using the official docker compose and recommended env properties, no SSO, but still get a HTTP 405 error when trying to log in.
I’m running on a local NAS setup (TrueNAS on ugreen NAS).
The docs were not really helpful as they contained wrong URLs. Using the container network names, I finally got Taiga running properly, but the last remaining issue is the login now:
or at least errors on the plugin are gone. but now im facing an issue on the account creation. Is taiga made to manually create the account and not based on other authentication methods? Taiga server config seems fine. Okta authentication is succesful and redirects normally. but then taiga server doesn’t recognize the credentials/account.
