-
Notifications
You must be signed in to change notification settings - Fork 81
Add test for ensuring keeping of displayname #137
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
Conversation
|
Codecov Report
@@ Coverage Diff @@
## master #137 +/- ##
============================================
+ Coverage 33.67% 33.74% +0.06%
+ Complexity 123 121 -2
============================================
Files 10 10
Lines 490 489 -1
============================================
Hits 165 165
+ Misses 325 324 -1
Continue to review full report at Codecov.
|
This code is a leftover from the old Shibboleth implementation from ownCloud days, nowadays it causes more issues than it does good (such as nextcloud/user_saml#137). Let's remove it for the future thus. Signed-off-by: Lukas Reschke <[email protected]>
Signed-off-by: Lukas Reschke <[email protected]>
`\OC_User::loginWithApache` sets the display name otherwise to the login name which is wrong. Signed-off-by: Lukas Reschke <[email protected]>
Signed-off-by: Lukas Reschke <[email protected]>
Signed-off-by: Lukas Reschke <[email protected]>
c13c09e to
a5a406f
Compare
Otherwise users can change their display name and email address which is in a SAML scenario undesired. Signed-off-by: Lukas Reschke <[email protected]>
|
Sent to owner of affected instance and awaiting feedback. |
|
This array index reminds me of another PR or was this in user_saml? 🤔 |
https://github.com/nextcloud/user_saml/pull/132/files?w=1 |
There seems to be a bug here, let's try to track it down with integration tests.
Fixes #119, fixes #125
Signed-off-by: Lukas Reschke [email protected]