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

Allow requests to custom endpoints in v4 #465

Open
erhan-backupta opened this issue Jun 7, 2024 · 4 comments
Open

Allow requests to custom endpoints in v4 #465

erhan-backupta opened this issue Jun 7, 2024 · 4 comments
Labels
enhancement New feature or request stale Triaged

Comments

@erhan-backupta
Copy link

erhan-backupta commented Jun 7, 2024

Describe the feature request?

In v4, there are some Okta API endpoints that're not supported by the SDK, such as the beta /api/v1/org/factors endpoint.
It would be good if we could send API requests even if they're not directly supported via SDK.

If this is a problematic request, even just exporting APIClient.prepareRequest function would help a lot.

New or Affected Resource(s)

All unsupported endpoints (e.g: Factor administration), or any recent endpoints added to API but not yet available in SDK versions

Provide a documentation link

https://developer.okta.com/docs/reference/api/factor-admin/#get-org-factor

Additional Information?

In v2 we were able to send custom requests easily as the example below:

req, _ := client.CloneRequestExecutor().NewRequest("GET", urlStr, nil)
resp, err = client.CloneRequestExecutor().Do(oktaCtx, req, nil)
@erhan-backupta erhan-backupta added the enhancement New feature or request label Jun 7, 2024
Copy link

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

@duytiennguyen-okta
Copy link
Contributor

OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-742335

Copy link

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

Copy link

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

@github-actions github-actions bot added the stale label Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Triaged
Projects
None yet
Development

No branches or pull requests

2 participants