LoCo Team Portal

SSO login should define what information is required, not allow a user to select what information to give

Bug #944473 reported by Erwin Heitzman
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Fix Released
Medium
Adnane Belmadiaf
LoCo Team Portal 0.3.11
Summit
Fix Released
Medium
Chris Johnston
Summit 1.2.1

Bug Description

Currently when a user attempts to login, we ask the user if they will share certain required information with us, and if they won't, we produce an error and do not let the user login.

What we should do is use SSO to require certain information instead of providing the user the choice.

I believe this goes against the SSO guidelines as we should be able to cope without having all the information that we want, however this doesn't work well for the use cases we have.

See original description

Related branches

lp:~cjohnston/summit/sso-req
Chris Johnston: Approve
Diff: 11 lines (+1/-0)
1 file modified
summit/settings.py (+1/-0)
Revision history for this message
Adnane Belmadiaf (daker) wrote :

Can you please detail where/what have you done ?

Changed in loco-team-portal:
status: New → Incomplete
Revision history for this message
Adnane Belmadiaf (daker) wrote :

Now i see what you mean.

Changed in loco-team-portal:
importance: Undecided → Medium
status: Incomplete → Triaged
Chris Johnston (cjohnston)
summary: - login required nickname while full name and email ticked
+ SSO login should define what information is required, not allow a user
+ to select what information to give
description: updated
Changed in summit:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Chris Johnston (cjohnston) wrote :

This has been committed as best as we can. To do any further we would have to be known by the SSO provider, which we are currently unable to do. The current fix that has been implemented for both (not yet released) is that the email and nickname field are marked required by Summit, which will check them by default. A user would then be required to uncheck them for us to not get the information.

Changed in summit:
status: Triaged → Fix Committed
assignee: nobody → Chris Johnston (chrisjohnston)
Chris Johnston (cjohnston)
Changed in summit:
milestone: none → 1.2.1
Adnane Belmadiaf (daker)
Changed in loco-team-portal:
status: Triaged → Fix Committed
assignee: nobody → Adnane Belmadiaf (daker)
Chris Johnston (cjohnston)
Changed in summit:
status: Fix Committed → Fix Released
Adnane Belmadiaf (daker)
Changed in loco-team-portal:
milestone: none → 0.3.11
Adnane Belmadiaf (daker)
Changed in loco-team-portal:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.