So, I have a React front-end, with a .NET core web api. Currently, I have Google setup within my Okta tenant as an Identity Provider, and auth is working as expected. After successful auth, a UserProfile is created within Okta UD, successful redirection back to my React client and life is good.
My question is in lieu of creating Google (or any other IdP) as a Identity Provider within my tenant, can I use, for example, the React/Google sdk, auth with Google directly, retrieve an id_token, validate that token with Google on my backend, and then mint an access_token by leveraging Okta? (id_token from Google, access_token issued by Okta), rather than after validating the id_token, minting my own access_token and bypassing Okta?
I suppose the catalyst for my question began around cost. I assume that with the first option, once the UserProfile is created within my Okta tenant, and said user logs in, that counts against my MAU’s.
Any guidance here would be greatly appreciated.