Fix Okta OIDC #11718
Merged
Fix Okta OIDC #11718
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zmb3
commented
Apr 4, 2022
zmb3
added
the
release-notes
|
For release notes: This fixes the following error when attempting to use Okta as an OIDC provider: |
atburke
approved these changes
Apr 4, 2022
codingllama
approved these changes
Apr 5, 2022
|
@russjones in order to get Okta OIDC working you need this PR and you also need to set Any objection to adding support for |
|
Yeah, add I had to do something similar for JumpCloud: #11805 |
zmb3
force-pushed
the
zmb3/fix-okta-oidc
branch
from
4551f4c to
f4aa4de
Compare
zmb3
force-pushed
the
zmb3/fix-okta-oidc
branch
from
f4aa4de to
966bae4
Compare
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
force-pushed
the
zmb3/fix-okta-oidc
branch
from
966bae4 to
eeacf60
Compare
zmb3
added a commit
that referenced
this pull request
Apr 14, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 14, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 14, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 14, 2022
This is the docs counterpart to #11718
Gregy
pushed a commit
to Gregy/teleport
that referenced
this pull request
Apr 14, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
* Document Okta OIDC provider workaround This is the docs counterpart to #11718 * Update docs/pages/enterprise/sso.mdx Co-authored-by: Paul Gottschling <[email protected]> Co-authored-by: Paul Gottschling <[email protected]>
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
* Document Okta OIDC provider workaround This is the docs counterpart to #11718 * Update docs/pages/enterprise/sso.mdx Co-authored-by: Paul Gottschling <[email protected]> Co-authored-by: Paul Gottschling <[email protected]>
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
* Document Okta OIDC provider workaround This is the docs counterpart to #11718 * Update docs/pages/enterprise/sso.mdx Co-authored-by: Paul Gottschling <[email protected]> Co-authored-by: Paul Gottschling <[email protected]>
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
* Document Okta OIDC provider workaround This is the docs counterpart to #11718 * Update docs/pages/enterprise/sso.mdx Co-authored-by: Paul Gottschling <[email protected]> Co-authored-by: Paul Gottschling <[email protected]>
This was referenced Apr 15, 2022
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
Using the OIDC connector with Okta would fail due to an issue in our fork of go-oidc. Update this dependency to get the fix. Additionally, clean up the logic for syncing the connector configuration, which was using a context.Context in order to implement a timeout. This can be expressed in a simpler way with time.After()
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
This is the docs counterpart to #11718 Backports #11948 Co-authored-by: Paul Gottschling <[email protected]>
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
This is the docs counterpart to #11718 Co-authored-by: Paul Gottschling <[email protected]>
zmb3
added a commit
that referenced
this pull request
Apr 15, 2022
This is the docs counterpart to #11718 Co-authored-by: Paul Gottschling <[email protected]>
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the OIDC connector with Okta would fail due to an issue in our
fork of go-oidc. Update this dependency to get the fix.
Additionally, clean up the logic for syncing the connector
configuration, which was using a context.Context in order to implement
a timeout. This can be expressed in a simpler way with time.After()