-
Notifications
You must be signed in to change notification settings - Fork 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
Evolve oidc logout #4986
Evolve oidc logout #4986
Conversation
👷 Deploy request for nginx-kubernetes-ingress pending review.Visit the deploys page to approve it
|
Thank you @llomgui |
Thank you @llomgui for submitting. Would it be possible for you to submit a GitHub issue to describe the situation you are trying to address. See CONTRIBUTING.md for a description of the issue submission process. There is also the scheduled community call where issues can be discussed. |
Hello @pdabelf5, |
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.
LGTM on the docs side. Withholding from an approval since much of the PR is code-based.
Hi @llomgui, We reviewed your issue and the team recommendation is to get the contents of your PR and port it into the Open ID connect reference implementation |
@danielnginx I will create a PR on this repository. Do I have to close this one? I don't see any link with Kubernetes-ingress. |
@llomgui thank you. Once that PR is merged in the nginx-openid-connect, files should get copied over to https://github.com/nginxinc/kubernetes-ingress/tree/main/internal/configs/oidc via a PR. You can close this PR for now. |
@danielnginx The PR created on OIDC repository does not include operators changes. |
@llomgui you are right, we can leave this PR open. Once we get the nginx-openid-connect PR in we can update here. |
@danielnginx Do you have any news on this PR? |
As @danielnginx said, we can merge this PR as soon as your PR in the nginx-openid-connect repo is approved and merged. If you need more visibility on PR, you can post about it in the public #nginx-users slack channel. The maintainers of the nginx-openid-connect repo frequently monitor that channel. |
Hello @llomgui, the nginx-openid-connect now includes support for OIDC logout, and our repository has been updated accordingly. We are keen to work with you to get this pull request merged. Could you align the OIDC files in your pull request with those in our kubernetes-ingress repository? |
@@ -243,6 +243,9 @@ func validateOIDC(oidc *v1.OIDC, fieldPath *field.Path) field.ErrorList { | |||
if oidc.AuthEndpoint == "" { | |||
return field.ErrorList{field.Required(fieldPath.Child("authEndpoint"), "")} | |||
} | |||
if oidc.LogoutEndpoint == "" { |
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.
I am not sure if logoutEndpoint
and redirectPostLogout
should be required fields. This will lead to a breaking change for current users looking to upgrade to the new release, as they will need to modify their OIDC configurations.
Hi @llomgui, we are closing this PR and our team is taking over the #4989 implementation. You can follow the progress in the issue, we are working on it in our current sprint https://github.com/orgs/nginxinc/projects/2 |
Proposed changes
Make sure the IDP is triggered during a logout.
Checklist
Before creating a PR, run through this checklist and mark each as complete.