Giter Club home page Giter Club logo

Comments (9)

siacomuzzi avatar siacomuzzi commented on July 16, 2024 1

I can reproduce the issue, we'll work on it. In the meantime, you can apply your workaround (if (id) opts.inResponseTo = id;)

from node-samlp.

mcastany avatar mcastany commented on July 16, 2024

Hello @yesvivek

I was reviewing the implementation of the auth function and the ID used as InResponseTo in the SAMLResponse is taken from the SAMLRequest unless you explicit set it as an option

https://github.com/auth0/node-samlp/blob/master/lib/samlp.js#L174-L175

Can you check the following:

  • You are not explicitly setting the InResponseTo when calling samlp.auth(options)
  • Your SAMLRequest has different IDs

from node-samlp.

yesvivek avatar yesvivek commented on July 16, 2024

@mcastany , My SAMLRequest has different IDs for each request. Am setting destination and all REQUIRED options when calling samlp.auth.

https://github.com/auth0/node-samlp/blob/master/lib/samlp.js#L175
This seems to be causing this issue for me. Changing it to if (id) opts.inResponseTo = id; works for me.
What do you suggest?

from node-samlp.

siacomuzzi avatar siacomuzzi commented on July 16, 2024

Could you please check the value of opts.inResponseTo before line 175? https://github.com/auth0/node-samlp/blob/master/lib/samlp.js#L175

from node-samlp.

yesvivek avatar yesvivek commented on July 16, 2024

Have added the below line as recommended in above comment.
console.log( "Dom ID: " + id + " VS opts.inResponseTo: " + opts.inResponseTo);

Results after multiple SAMLRequests:

1. Dom ID: id175479885406247111143820862 VS opts.inResponseTo: undefined
2. Dom ID: id13229522944305032913039188 VS opts.inResponseTo: id175479885406247111143820862
3. Dom ID: id175429005758588441628725185 VS opts.inResponseTo: id175479885406247111143820862
4. Dom ID: id175496083313503221789498695 VS opts.inResponseTo: id175479885406247111143820862

from node-samlp.

siacomuzzi avatar siacomuzzi commented on July 16, 2024

try with [email protected]

thanks for reporting!

from node-samlp.

yesvivek avatar yesvivek commented on July 16, 2024

Thanks for the quick patch! It works awesome now.

from node-samlp.

siacomuzzi avatar siacomuzzi commented on July 16, 2024

But this is incompatible with my Service Provider

do you know why? InResponseTo contains the ID of the initial SAMLRequest.

from node-samlp.

paulocheque avatar paulocheque commented on July 16, 2024

Don't know. But I close the issue since I saw what creates this id. Thanks.

from node-samlp.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.