Closed markhuot closed 4 years ago
I posted a similar question over to the SAML project and got a helpful response:
https://github.com/simplesamlphp/saml2/issues/188#issuecomment-567482164
Not sure if this should be calling validateSignature
instead?
I'll take a look.
Thank you Damien! I'm happy to provide any other detail you may need, just let me know.
@markhuot I found where you can configure the key under the SSO tab within OneLogin so that it matches the correct signature algorithm. (see screenshot)
I can get past the error you are seeing but I'm not getting past the the validation of the signature once those are aligned. I haven't worked with OneLogin before. Not sure what they are doing differently but I must be missing something here.
How about you see if what I point out above works for you and then we can move from there. I assume you'll see the same. Timing right now with the holidays is pretty tight so I'm not sure when I'll be able to dive deeper into this.
OneLogin does have this php lib which might be a good reference to what I might be missing.
Thanks @dsmrt, I'm seeing the same thing as you. I changed mine to SHA-512 to get past the signature issue (since my x509 cert is SHA-512, I think…) and then I hit the Assertion error. If I change it back to SHA-256 I get the signature error but presumably the assertion would go through.
I'll dig in to the OneLogin PHP lib and see if there's anything interesting they're doing in there.
I think I found the issue here. Run a composer update flipboxfactory/saml-core
and see if that works for you. I was also able to change the Signiture Algorithm to SHA512 and it worked with that setting as well. Let me know if this works out for you!
Thanks @dsmrt, I'll check it out today!
@dsmrt, I got tied up on Friday and didn't get a chance to test this until just now but it's working great! Thank you so much for the fixes to support OneLogin, this is fantastic news!
Hi, I'm integrating with OneLogin and am running in to some hashing difficulties that I can't tell if they are a fault of the OneLogin response or something in this plugin. The easiest trace of the error is here,
It seems that the response from OneLogin comes back with an a SHA512 key but when
saml-core/src/validators/Response
calls->validateAssertions
it calls->validate
on theSAML2/Assertion
which expects a SHA256.Is this a misconfiguration I have some where?