PrivateSet - Authentication vs Authorization

Get Help and Help Others
1

PrivateSet has the ability to specify a page to be redirected to if you are unauthenticated (or not in the list of the authorized roles).

It feels like it should have two properties, one for this feature (unauthenticated) and another for the page to navigate the user to if they are authenticated but not authorised (unauthorized).

For example, you may want to send an unauthenticated user to the login page, but an unauthorized user to a forbidden page.

I suppose I could achieve it by making this property dynamic based on the user’s authenticated status, or perhaps something on the page I send the user to. But that doesn’t seem ideal.

Am I missing something and this feature is already included? Or am I thinking about this incorrectly and the framework wants me to take a different approach?

2

I think the answer to this is nesting:

<PrivateSet unauthenticated={'logIn'}>
        <PrivateSet unauthenticated={'unauthorised'} roles={['foo','bar']}>
                  <Route ..../>
        </PrivateSet>
</PrivateSet>