Redirect back to original secured route after login

Open
#385 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
authentication, frontend

Research direction

Start by tracing the secured-route authentication flow in @asgardeo/react-router and how the OAuth2 state parameter is created and handled after login. Confirm how valid secured paths are identified, then verify that a successful login restores the originally requested route instead of /.

Written by the indexing model from the issue text.

Description

Type/Improvement
Current Limitation

When using @asgardeo/react-router, navigating to a secured route without being logged in redirects the user to Asgardeo/IS for authentication.

After successful authentication, the user is redirected to the application root (/) instead of the originally requested secured route. This results in a poor user experience. Ideally, the user should be redirected back to the exact secured route they intended to access.

.

Suggested Improvement

This can be implemented without changes to Asgardeo/IS by leveraging the OAuth2 state parameter. The SDK can encode the currently active path in the state parameter (only if the route is valid and marked as secured) and restore it after successful authentication

Please select the package issue is related to

@asgardeo/react-router

Version

1.1.0

Reporter Checklist
  • I have searched the existing issues and this is not a duplicate.
  • I have provided all the necessary information.
  • I have verified the improvement is not available in the latest version of the package.
Dominant language
TypeScript
Stars
18
Forks
67
Avg merge
4h 6m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from asgardeo/javascript

All issues in asgardeo/javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.