mattbaumann1

Thank you for the quick response. I will have to look a little more closely. Thanks feel free to collapse or close this issue.

We had a bunch of IDP logout issues because of the session_index. You can see what we did on this ticket. I have been meaning to create a PR for...

We recently upgraded to v1.7.0 and started having this issue. I decided to push it to v1.9.0 with the hopes it would be fixed and ended up with the same....

I think this is going to be a cross-site issue that will include the installation of gem 'rack-cors'. Is this what was required for others?

For us this ended up being an issue with turbo_stream reloading not loading the necessary headers and a CORS error being thrown, so not associated with the devise_saml_authenticatable upgrade but...

Again, please close this issue if you (@adamstegman ) think it is inappropriate. I am working through the multiple authentication method described in the wiki. I am now working through...

@adamstegman, it isn't making a lot of sense to me. There is a @current_saml_user in the session and then there isn't. Here is a clip of the log from where...

@adamstegman , so far, I think the only conflict is with confirmable. I think you need to somehow set a value for user.confirmed_at on user creation from the saml response....

Sorry I should add that I am running two separate instances trying to get this running. One we ran into the problems above with the loss of the current_saml_user for...

Exactly, using a attr_accessor instead of storing it in the database. If it gets stored into the database and you open two browsers with two separate sessions, it overwrites the...