CL-16691: Support Okta Access token

[vyerawar-gfm]

No description provided.

[vyerawar-gfm]

We can pass okta generated access token to call endpoints
classy.me.retrieve({ token: { // Okta generated access token access_token: access_token, is_okta_token: true } })

[ESoch]

Where does this.baseUrl get set? I'd prefer that we update that value in the appropriate place if config.oktaBaseUrl is passed in.

[vyerawar-gfm]

this.baseUrl is set in src/ClassyResource/main.js. In that we are not getting request payload to check is_okta_token flag.
I am removing this change from here and updating the this.baseUrl value in src/ClassyResource/createMethod.js file. I have updated the code, please review.

[ESoch]

High level these changes look good. We'd want to make sure we have documentation that details what we're doing and why in the README and also comments in the code.

---

I'm going to hold off on "approving" for now. We'll want to look into how we can potentially publish your fork to our private registry so that we can do tests before we merge.

[vyerawar-gfm]

High level these changes look good. We'd want to make sure we have documentation that details what we're doing and why in the README and also comments in the code.

I'm going to hold off on "approving" for now. We'll want to look into how we can potentially publish your fork to our private registry so that we can do tests before we merge.

Hi @ESoch
README shows all related to app token, there is no anything related to member token and we have updated this for member token.
Also the changes that we are making are part of internal requirements. Can we discuss this with Kate, Arijeet, Stephan to decide if we want this information to be public.
Thank you.