-
Notifications
You must be signed in to change notification settings - Fork 45
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
Gerrit: ICLAs & CCLAs Process stop at "You are being redirected to the login page." #4240
Comments
- Resolved return url for the docusign flow Signed-off-by: Harold Wanyama <[email protected]>
@thakurveerendras kindly check. As you had identified earlier there was an auth issue . You can check the docusign gerrit flow |
Tested issue on dev site and found that it is reproducible when we login with different user (lf user which having different Gerrit email address) |
@thakurveerendras As confirmed with the production project JuanSebastian availed for testing... this is as well reproducible in prod and is not a regression issue |
@amolsontakke3576 thank you for looking into this, please let us know what is the latest for this ticket. Thanks! |
This is fixed in DEV as reported. Moving to QA. |
Confirmed the re-direction is working in Production for ICLA and CCLA. However, when the users perform an ICLA signature or proceed with ECLA for CCLA, the contributors should be added to the respective project LDAP group. This is currently not happening. Without this, even after signing, the users are unable to contribute, which is still a blocker. |
@jarias-lfx resolved the ldap group addition however changes have been deployed in dev |
We discovered that user was not added to LDAP. This is fixed and ready to deploy to PROD. |
- Handled nil pointer execption for auth user - Handled email send for icla - Added ldap group for corporate callback Signed-off-by: Harold Wanyama <[email protected]>
[#4240] Bug/LDAP Gerrit LDAP group addition
This is fixed and deployed to PROD so closing this ticket. |
Summary
Gerrit: ICLAs & CCLAs Process stop at the "You are being redirected to the login page."
Background
Steps:
Expected behavior
User should redirect to docusigned page
Screenshots
The text was updated successfully, but these errors were encountered: