feat: Enhance SDK Client to support Client ID and Secret Authorization
PR Checklist
Please check if your PR fulfills the following requirements:
- [x] The commit message follows our guidelines
- [x] Tests for the changes have been added (for bug fixes / features)
- [x] Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
- [ ] Bugfix
- [x] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Adding Tests
- [ ] Build related changes
- [ ] CI related changes
- [x] Documentation changes
- [ ] Other... Please describe:
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?
- [ ] Yes
- [x] No
Other information
Reviewers
@jefftaylor-okta
@ryanbradley
@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?
@bretterer @jaredperreault-okta Bump
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?
@bretterer @jefftaylor-okta @jaredperreault-okta Any updates on when this might be able to go in?
Any updates on when this can go in?