
JonathanK.96482 (Customer) asked a question.
We have a single-page web app that I have successfully integrated with an Okta OIDC app. I now need to connect a traditional web app to the same Okta OIDC app. The problem is that the SPA app in Okta doesn't give me an OAuth2 client_secret. How do I configure the Okta app to support both SPA and server-side web app auth flows?

Hi @JonathanK.96482 (Customer) , Thank you for reaching out to the Okta Community!
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work).
That being said, I did check in with my colleagues and confirmed that this is not supported, unless we've misunderstood your request.
SPA will not have a Client Secret and a Web app will. There's no way to have a single client that both does and does not have a client secret (that is both a Public client and a Confidential client, as described here: https://datatracker.ietf.org/doc/html/rfc6749#section-2.1).
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
💡 Community Moderator Tip: Join a group today and connect with other Okta customers by region or product.