sfrunza13
sfrunza13
I have just come across this repo and am still getting to understand it but I would like to see if I could do this if that's alright. It might...
Update, started working on this and got my first ephemeral to send, I will open a draft PR soon so everyone can see what I am attempting to do
> cc @sfrunza13, this is what you were hitting too. It is, how would I go about debugging this?
From the documentation of passport-SAML on NPM they claim that there should be a bodyparser middleware called before `passport.authenticate('saml');` `bodyParser.urlencoded({ extended: false })` which uses a different query string parser...
I can not seem to replicate the issue with my local docker container setup using simplesaml storing session in either Redis or Memory.
> We do this before we add the SAML stuff: > > https://github.com/Seneca-CDOT/telescope/blob/master/src/satellite/src/app.js#L31-L34 Not sure if changing this could make a difference in prod or not, but there is an...
## From the passport-saml docs >Provide the authentication callback You need to provide a route corresponding to the path configuration parameter given to the strategy: >The authentication callback must be...
It's definitely not likely but it's one of the only things I could think of, now not even being able to re-create the problem anymore I really am lost.
`connect-sid` missing in cookies on the req header of the callback when we get the 400
I am interested to know how maintainers envision this feature being added. Is this idea of having another line in the yaml a good idea? Should the ephemeral be an...