Closed lucascudo closed 5 years ago
I am also getting this when the NameIDPolicy is set to urn:oasis:names:tc:SAML:2.0:nameid-format:transient, could this be an issue with using SAML 2?
I am using SAML 2 as well, but, but in my metadata.xml the directive is called NameIDFormat and it is set to urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.
What was the issue/solution? I ended up commenting out that check and it seems to work, but probably not ideal.
I am facing this issue too.
LightSamlModelException: NameID value not set
I can't figure out where the problem is. I have 2 service providers with nearly identical configs. One works (destination https://sptest.iamshowcase.com/acs) , the other one doesn't. Both configs have:
'nameID' => 'email'
This request is working:
`<samlp:AuthnRequest
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
ForceAuthn="false"
ID="ab9625f3fa1286566ae35108319fc0d9b7e602beb"
IssueInstant="2019-04-06T14:51:37Z"
Destination="[my login url]"
AssertionConsumerServiceURL="https://sptest.iamshowcase.com/acs"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Version="2.0">
Hello,
I am aparently facing same problem described at https://github.com/kingstarter/laravel-saml/issues/12 and https://github.com/kingstarter/laravel-saml/issues/15 , wondering if someone has figured out how to resolve that?