We are providing a web application for our customers, external, we have enabled self-service registration and are hosting the Okta Sign-In widget ourselves in our ReactJS application.

I have disabled the show sign-up on our Okta login so only our custom built apps will show the sign-in option and not our Okta tenant itself.

So our ReactJS app presents the Okta Sign-In widget, the public (people) will sign-up, first name, last name, email address. Once they have registered, Okta states it will redirect back to the customer (OIDC) application, which it does, however, they cannot access our custom ReactJS app because we will be checking if they are a valid, authenticated, and authorised user, i.e. the user would need to be in a group assigned to the OIDC application.

Does anyone know how we achieve such a simple, basic task, this seems very simple, we've even written our own IDP based on Identity Server 4.0 in the past, but ditched it for Okta instead. However, Okta doesn't seem to offer all the functionality it appears should just be there, and easy out of the box. Even the Self-Registration feature is global, whereas it should be application scoped, Okta is either missing something, or we just aren't getting how Okta have gone about this. I hope it's just us, and we can't seem to see it.

Can anyone help please?