Closed JuancaG05 closed 5 months ago
QA Checks over authorize
request in login and re-login processes
One consideration:
I noticed this is affecting the legacy webfinger flow somehow: if send_login_hint_and_user
is true, the username is propagated from the login view to the idP. If if send_login_hint_and_user
is false, it is not. Since the feature and the new parameter should only affect the re-login process as defined, this might need a look.
I also noticed that scope
and prompt
are sent empty to OAuth2, because they are OIDC parameters. This is not in the scope of this PR, i will check and open issue in order to discuss whether that behaviour could be improved.
I noticed this is affecting the legacy webfinger flow somehow: if send_login_hint_and_user is true, the username is propagated from the login view to the idP. If if send_login_hint_and_user is false, it is not. Since the feature and the new parameter should only affect the re-login process as defined, this might need a look.
this is the expected behaviour since the login and relogin calls are the same. We can not prevent the side-effect is attached to the branding decision regarding the send_login_hint_and_user
parameter.
Let's move this forward
Related Issues
App: https://github.com/owncloud/android/issues/4288
QA
https://github.com/owncloud/android/pull/4291#issuecomment-1907946457