Skip to content

feat: support external auth token for Folksonomy editor#463

Open
swastikCommits wants to merge 1 commit intoopenfoodfacts:mainfrom
swastikCommits:feat/accept_keycloak_token
Open

feat: support external auth token for Folksonomy editor#463
swastikCommits wants to merge 1 commit intoopenfoodfacts:mainfrom
swastikCommits:feat/accept_keycloak_token

Conversation

@swastikCommits
Copy link
Copy Markdown
Contributor

What

Implemented the external token injection :

  • Added an auth-token property to the <folksonomy-editor> and <folksonomy-editor-row> components.
  • Updated the internal API layer (makeAuthenticatedRequest) to prioritize this external token if provided.
  • Bypassed the default auth_by_cookie flow when an external token is present to ensure compatibility with host applications like Explorer auth states.

Part of

openfoodfacts/openfoodfacts-explorer#1145

@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 14, 2026

@swastikCommits is attempting to deploy a commit to the openfoodfacts Team on Vercel.

A member of the Team first needs to authorize it.

@VaiTon
Copy link
Copy Markdown
Member

VaiTon commented Apr 6, 2026

I'd rather not embed the token in the DOM, instead pass a modified fetch that appends the token. What do you think?

@VaiTon
Copy link
Copy Markdown
Member

VaiTon commented Apr 20, 2026

Or, use the configuration component and add a function to it that "saves" the token in memory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants