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

orgid attribute from SAML response not used on user creation #5042

Closed
bloo-dye opened this issue Apr 11, 2024 · 2 comments
Closed

orgid attribute from SAML response not used on user creation #5042

bloo-dye opened this issue Apr 11, 2024 · 2 comments
Labels

Comments

@bloo-dye
Copy link

Detailed description of the problem

Was looking into the fallback from email to internal ID with saml, but it seems the internal ID is never synchronized in the first place.

Expected Behavior

In the docs it is mentioned that orgid is going to be set for user creation on the fly.

Steps to reproduce the behavior

Register user with SAML. Internal ID remains "unset"

What eLabFTW version are you using? Visible in bottom right of a page.

5.0.4

Do you have any idea what may have caused this?

I checked the saml.php and it seems the parameter orgid is not used on user creation. The orgid can be added to the function "getUser" (as well as "fromExternal"/"fromScratch" down the line). This works as long a the team is not interactively selected by the user.
In the public function "createOne" the optional parameter orgid is already present.

Do you have an idea how to solve the issue?

Not sure how to deal with when team is selected by user.

Additional information

No response

@bloo-dye bloo-dye added the bug label Apr 11, 2024
@NicolasCARPi
Copy link
Contributor

I guess the orgid information must be carried over with the name/email during team selection.

@NicolasCARPi
Copy link
Contributor

Fixed in #5048

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

No branches or pull requests

2 participants