Bug : API v2 auth token creation fails due to token request field mismatch

[Shikshak-Kumar]

Description

Token creation via API v2 fails because the frontend sends snake_case
token request fields, while the backend expects camelCase fields.

Steps to Reproduce

1. Build FOSSologyUI pointing to API v2:

NEXT_PUBLIC_SERVER_URL=localhost/repo/api/v2

2. Attempt to create a new authentication token via the UI or REST call.
3. Observe token creation failure or missing token metadata.

Expected Behavior

Token should be created successfully with correct token name, scope,
and expiry.

Actual Behavior

Token metadata is ignored or token creation fails because the backend
does not recognize the provided request fields.

Root Cause

The backend TokenRequest::fromArray() explicitly expects camelCase
fields (tokenName, tokenScope, tokenExpire), but the frontend
sends snake_case fields (token_name, token_scope, token_expire).

Environment

• FOSSologyUI version: main branch
• API version: v2
• OS: macOS (Apple Silicon)
• Browser: Chrome

Additional Context

This issue only affects API v2 authentication token creation.

[Shikshak-Kumar]

@GMishx @shaheemazmalmmd
I’d like to work on this issue and submit a pull request. Could you please confirm if I can proceed?

[shaheemazmalmmd]

@Shikshak-Kumar : issue is assigned to you.

[Shikshak-Kumar]

@shaheemazmalmmd , I’ve raised PR #349 to address the issue. Please review it.

[work-akshay05]

@shaheemazmalmmd hey, if this is still open, I would love to solve this

[Qasimahmad55]

I would love to solve this issue can you assign it to me?

[SagarKhatri649]

@shaheemazmalmmd Hi! I’d like to work on this issue and open a PR.

It looks like API v2 expects camelCase (tokenName, tokenScope, tokenExpire) but the UI sends snake_case (token_name, token_scope, token_expire), which breaks token creation / metadata. I noticed an earlier PR was raised but isn’t active now.

If it’s okay, I can submit a fresh PR to align the request fields and verify using NEXT_PUBLIC_SERVER_URL=localhost/repo/api/v2.

Could you please assign this issue to me or confirm I should proceed? Thanks!