authgear / authgear/authgear-server

Easy to trigger invalid session

Open
#3,552 2 comments 0 reactions 0 assignees View on GitHub
cooldown/enhancement
Dominant language
Go
Stars
2k
Forks
125
Avg merge
2d 17h
Merged PRs (30d)
32

Description

## Problem

It's easy to trigger the "Direct Access disallowed" in the web apps
for example, user quit and reopen the mobile browser.
They will see a cryptic message

> ## Direct access to this page is disallowed
>
> This page can only be accessed via the authorization endpoint.

## Proposed change

1. Change the message to a more user-friendly one
1. To be handled in [DEV-350 : Improve error page for CSRF Error page​](https://linear.app/authgear/issue/DEV-350/improve-error-page-for-csrf-error-page)
2. Switch to a Max-Age cookie of 5 minutes. Each request will extend the age by 5 minutes.

Please also research if giving up session cookie is ok security-wise

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by tracing the web-app session-cookie handling and the “Direct access to this page is disallowed” path, then review the linked DEV-350 issue and investigate the security implications of the proposed cookie change. Done means the invalid-session experience is user-friendly, the cookie behavior is implemented as agreed, and the security research is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.