This example utilizes a development namespace (auth10-dev) on Windows Azure Access Control Service and is using Google as the only identity provider configured for the sample application.
passport.use(newwsfedsaml2(
{
path:'/login/callback',
realm:'urn:node:app',
homeRealm:'',// optionally specify an identity provider to avoid showing the idp selector
This example utilizes a strategy with ADFS using WS-Fed.
passport.use('wsfed-saml2',newwsfedsaml2({
// ADFS RP identifier
realm:'urn:node:wsfedapp',
identityProviderUrl:'https://my-adfs/adfs/ls',
// ADFS token signing certificate
thumbprint:'5D27....D27E'
// or cert: fs.readFileSync("adfs_signing_key.cer")
},function(profile,done){
// ...
}));
Configure strategy for ADFS (SAMLp)
This example utilizes a strategy using SAMLp and RP token encryption.
passport.use('wsfed-saml2',newwsfedsaml2({
// ADFS RP identifier
realm:'urn:node:samlapp',
identityProviderUrl:'https://my-adfs/adfs/ls',
// ADFS token signing certificate
thumbprint:'5D27...D27E',
// or cert: fs.readFileSync("adfs_signing_key.cer")
protocol:"samlp",
// This is the private key (use case where ADFS
// is configured for RP token encryption)
decryptionKey:fs.readFileSync("server.key")
},function(profile,done){
// ...
}));
Issue Reporting
If you have found a bug or if you have a feature request, please report them at this repository issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
Security Notice
The Security Notice lists the version that is vulnerable and the actions that are required to upgrade to the latest version.