-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Improving flow when user denies Bitbucket access to Che #19620
Conversation
Signed-off-by: xbaran4 <pbaran@redhat.com>
Can one of the admins verify this patch? |
Signed-off-by: xbaran4 <pbaran@redhat.com>
Signed-off-by: xbaran4 <pbaran@redhat.com>
what about unit tests? |
Please merge the latest master to fix the build check. |
Signed-off-by: xbaran4 <pbaran@redhat.com>
...-core-api-auth/src/main/java/org/eclipse/che/security/oauth1/OAuthAuthenticationService.java
Show resolved
Hide resolved
If there are not any apparent issues, I believe this PR can be merged in order to help with dashboard reaction implementation. I will provide tests for OAuthAuthenticationService in a subsequent PR. Testing this PR is described above. It was also tested by me in the current state. |
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.
Ok for me to merge the code and add tests in separate pr
Signed-off-by: xbaran4 pbaran@redhat.com
What does this PR do?
After user denies authorization of che with bitbucket they are redirected to redirect_after_login URI with error query parameter.
Screenshot/screencast of this PR
What issues does this PR fix or reference?
Improve workflow when user denies Bitbucket access for Che #19274
How to test this PR?
https://www.eclipse.org/che/docs/che-7/administration-guide/configuring-authorization/#proc_configuring-bitbucket-server-oauth1_che)
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.