Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

identifierFormat example for ADFS not correct #234

Closed
cburatto opened this issue Sep 11, 2017 · 1 comment
Closed

identifierFormat example for ADFS not correct #234

cburatto opened this issue Sep 11, 2017 · 1 comment

Comments

@cburatto
Copy link

On the documentation, Usage with Active Directory Federation Services:

{
entryPoint: 'https://ad.example.net/adfs/ls/',
issuer: 'https://your-app.example.net/login/callback',
callbackUrl: 'https://your-app.example.net/login/callback',
cert: 'MIICizCCAfQCCQCY8tKaMc0BMjANBgkqh ... W==',
authnContext: 'http://schemas.microsoft.com/ws/2008/06/identity/authenticationmethod/windows',
identifierFormat: null
}

However, the metadata generated by generateServiceProviderMetadata shows an empty <NameIDFormat/>.

This seems to be because the saml.js code is:

if (options.identifierFormat === undefined) {
    options.identifierFormat = "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress";
  }

It should probably test for undefined and null.

@cburatto
Copy link
Author

cburatto commented Sep 14, 2017

Scrap that: it seems you can really NOT send any identifier on the request, and the only way to do that is using identifierFormat = null. If you simply ommit identifierFormat from the options, it will default to urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant