-
Notifications
You must be signed in to change notification settings - Fork 274
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
Sponsor choose access duration #4061
Sponsor choose access duration #4061
Conversation
@jrouzierinverse To review and @lzammit to test. |
rebase |
f21817a
to
b774941
Compare
Rebased. |
Looks good @lzammit please test |
@jrouzierinverse Correct me if I'm wrong here but the new GUI needs to be modified for this too. It'll have to be adjusted by @satkunas prior merging or immediately after. |
Yes as it adds a new field in Sponsor sources |
670f03b
to
b774941
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved!
If approved , can we merge ? |
Did Zammit test it? |
Not part of his test to do. |
I update NEWS section of the description to add "Define which authentication source used to verify that the sponsor is allowed to sponsor", see #3631. Thanks @jrouzierinverse |
b774941
to
e9b050c
Compare
@satkunas the new admin GUI needs to be adjusted for this PR |
@satkunas can you help for the new admin ? |
e9b050c
to
b56d7f2
Compare
(back end) rename choose_access_duration to set_access_durations to match current set_access_duration
b56d7f2
to
60f3d3a
Compare
Retested from the new admin gui and register on the portal. |
Should we move that to v9.1? It's currently targeted for 9.2. |
Description
Allow the sponsor to choose the access duration
Define which authentication source used to verify that the sponsor is allowed to sponsor.
Impacts
Sponsor flow
Delete branch after merge
YES
Checklist
NEWS file entries
New Features