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
Hi,
I'm trying to setup SAML auth with our Shibboleth IDP but seems like something is not quite right. I'm running SnipeIT v6.1.2 and am able to setup SAML and reach our shibboleth login page and authenticate successfully (per my idp logs). But when it returns to the application I get a 500 error. I have already created the user in snipeit.
The only thing I've been able to find by searching is where @misilot mentioned it at #10055 where it was mentioned that its working with shibboleth. Our Shib idp is v4. The weird thing is that I don't see any logs on the snipeit side to understand what's throwing the 500 error. I've disabled/enabled SAML multiple times and rebooted the VM as well but no luck on the logs. Apache logs just show the GET request for the saml/acs path and the laravel.log hasn't been updated in over a week for some reason.
If anyone can share their experience or provide any suggestions, I'd really appreciate it.
Thanks
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm trying to setup SAML auth with our Shibboleth IDP but seems like something is not quite right. I'm running SnipeIT v6.1.2 and am able to setup SAML and reach our shibboleth login page and authenticate successfully (per my idp logs). But when it returns to the application I get a 500 error. I have already created the user in snipeit.
The only thing I've been able to find by searching is where @misilot mentioned it at #10055 where it was mentioned that its working with shibboleth. Our Shib idp is v4. The weird thing is that I don't see any logs on the snipeit side to understand what's throwing the 500 error. I've disabled/enabled SAML multiple times and rebooted the VM as well but no luck on the logs. Apache logs just show the GET request for the saml/acs path and the laravel.log hasn't been updated in over a week for some reason.
If anyone can share their experience or provide any suggestions, I'd really appreciate it.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions