NIFI-4889: Logout not working properly with OIDC#2830
NIFI-4889: Logout not working properly with OIDC#2830Trojan295 wants to merge 1 commit intoapache:masterfrom
Conversation
|
When running the test suite locally I have problems with an dependency: I had to add an additional repository to make it work, although I didn't commit it: Could it be, that the artifact was in Maven Central and was moved, but the CI on Travis as it cached in the local repo? |
|
@Trojan295 - NiFi 1.7.0 has been released, I'd recommend you to rebase against master (so that all the pom files are updated to 1.8.0-SNAPSHOT) and do a full build to have a clean local maven repo (you shouldn't have 1.7.0-SNAPSHOT anymore). All the Travis builds are OK for your PR so it sounds OK to me. Regarding the PR itself, I'll let someone like @mcgilman having a look ;) |
|
Rebased from current master |
|
Will review... |
|
@Trojan295 Thanks for the PR! The code looks good but I ran into an issue when attempting to log out. Despite being a required field in the openid spec [1], it appears that at least in practice [2] the [1] https://openid.net/specs/openid-connect-session-1_0.html#OPMetadata |
|
I added a fallback to simply redirect back to NiFi in case the end session endpoint isn't present. Tricky thing is, that NiFi automatically starts an login attempt, when an unauthenticated user accesses NiFi. In case of an IDP like Keycloak, which has the end session endpoint, then after logout the user is redirected back to Keycloaks login page. In case of Google OpenID he gets redirected to them and the SSO mechanism logs the user again... |
- Redirect user agent to end session endpoint on the OIDC provider
|
Looks good @Trojan295. Thanks! This has been merged to master. |
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically master)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.