-
Notifications
You must be signed in to change notification settings - Fork 61
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
feat: Enhance SDK Client to support Client ID and Secret Authorization #426
base: master
Are you sure you want to change the base?
Conversation
@jaredperreault-okta Can you have a look at this PR? |
@bretterer I cleaned up the commits so they would all be verified as per you repo merge rules. Can you re-approve the PR since your initial review was dropped after I cleaned up the commits? |
@bretterer thanks for the review here- for some reason, @Astro2024 and I can't merge this PR. Anything else we need to do? |
@jaredperreault-okta are there any other steps we need to take to get this PR Merged? |
Hey, any updates on this? We could really use this. Thanks! |
@bretterer @jefftaylor-okta @jaredperreault-okta Is there a timeline for when this PR can be merged or is there currently a moratorium on PR merges? |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently, there are two ways to initialize the Okta client within the okta-sdk. The first is using an api token and the second is using a public private key pair.
Issue Number: N/A
What is the new behavior?
This PR allows someone using the okta-sdk to initialize the Okta client using client id and client secret in addition to the previous two methods mentioned.
Does this PR introduce a breaking change?
Other information
Reviewers
@jefftaylor-okta