Authorize via client_secret and client_id (client_secret_post)

[anasinnyk]

Summary

This functionality provides the possibility to use Client Secret from Application for access to API. It's a client_secret_post method from okta configuraion We want to use it when installing our app from Catalog.

Fixes N/A

Type of PR

• [x] Bug Fix (non-breaking fixes to existing functionality)
• [x] New Feature (non-breaking changes that add new functionality)
• [x] Documentation update
• [x] Test Updates
• [ ] Other (Please describe the type)

Test Information

• [x] My PR required test updates

Go Version: 1.20.5 Os Version: MacOS OpenAPI Spec Version:

Signoff

• [ ] I have submitted a CLA for this PR
• [x] Each commit message explains what the commit does
• [x] I have updated documentation to explain what my PR does
• [x] My code is covered by tests if required
• [x] I ran make fmt on my code
• [x] I did not edit any automatically generated files

[github-actions[bot]]

This PR has been marked stale because there has been no activity within the last 28 days. To keep this PR active, remove the stale label.

[github-actions[bot]]

This PR has been marked stale because there has been no activity within the last 28 days. To keep this PR active, remove the stale label.

[monde]

Just following up here @anasinnyk . Technically, this PR is against v2 of our SDK and we aren't making changes to the v2 codebase. We are on v3 of the okta-sdk-golang and I believe @duytiennguyen-okta is going to promote v3 as the default release and update the master branch accordingly.

Also, in the coming year we have some changes to our language SDKs planned to better support client secret for machine-to-machine OAuth scenarios so that work may satisfy your ask.

@duytiennguyen-okta @jefftaylor-okta

[github-actions[bot]]

This PR has been marked stale because there has been no activity within the last 28 days. To keep this PR active, remove the stale label.