Skip to content
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

Jump to bottom

Ensure all OIDC application values are carried over in the spec #207

Closed
jmelberg-okta opened this issue Jul 20, 2018 · 3 comments
Closed

Ensure all OIDC application values are carried over in the spec #207

jmelberg-okta opened this issue Jul 20, 2018 · 3 comments
Labels
Analysis
Projects
Okta OSS Java

Comments

@jmelberg-okta
Copy link
Contributor

Carried over from internal repo: #132.

  • post_logout_redirect_uris are missing from OIDC Application settings.oauthClient
@bdemers bdemers added Analysis and removed Triaged labels Feb 25, 2019
@bdemers bdemers added this to To do in Okta OSS Java Mar 25, 2019
@shalinmangar
Copy link

Is there a workaround for this? I need to set a custom logout uri for an OIDC application.

@bdemers
Copy link
Contributor

bdemers commented Feb 12, 2020

Hey @shalinmangar!

You should be able to treat any of the resource objects like a map to set other properties.
For more complex objects you can do something like this too:
https://github.com/okta/okta-sdk-java#call-other-api-endpoints

@arvindkrishnakumar-okta
Copy link
Contributor

arvindkrishnakumar-okta commented Jul 8, 2020 •
edited

Update: Latest Open API Spec v2.0.0 (Java Mgmt SDK upgraded to v2.0.0 as well) carries all the OIDC application values.

Okta OSS Java automation moved this from To do to Done Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Analysis
Projects
Okta OSS Java
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@shalinmangar @bdemers @jmelberg-okta @arvindkrishnakumar-okta