jakartaee / jakartaee/authentication

Clarify state and concurrency expectations of Jakarta Authentication APIs

Open
#119 4 comments 0 reactions 1 assignee View on GitHub

@arjantijms is already working on this.

Since Jan 8, 2025.

EE12
Dominant language
Java
Stars
27
Forks
35
PR merge metrics
No merged PRs in 30d

Description

This issue is to explore and clarify the state expectations of the Jakarta Authentication APIs and the parameters passed to those APIs.

This is to follow up on some discussions regarding state in the CallbackHandler but I think we should also consider some of the Authentication APIs where state may be shared.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.