[QUESTION][ICA]: Error creating API token in ICA

[gayathrics2304]

Issue #1 - Error creating token: Insufficient permissions. Required: tokens.create Team - c1f07278a4a049009ab7950b6c0142bf I am facing an issue while generating an API Access Token (Bearer Token) to connect the MCP server from ICA to an agentic flow. While trying to create the token, I am getting a permission-related error (such as insufficient permissions like tokens.read / tokens.create). Due to this, the token is not getting generated successfully. Issue #2 - Error creating token: Unexpected token '<', "

ICA_Token_Issues.pdf

[crivetimihai]

Hi @gayathrics2304, thank you for reporting this! From the screenshots, it looks like you're on a very old version of ContextForge - can you specific the exact version please?

On the current version, I've investigated and verified the token creation behavior:

Issue 1 - "tokens.create Team - c1f07278a4a049009ab7950b6c0142bf"

The error message includes a team ID, which indicates ICA is calling the team token endpoint (/tokens/teams/{team_id}) rather than the personal token endpoint (/tokens).

Team token creation requires you to be an active member of that team. The error you're seeing is expected if you're not a member of team c1f07278a4a049009ab7950b6c0142bf.

To create a personal API token (recommended for individual use):

• Use the /tokens endpoint (POST request without team ID)
• Any authenticated user can create personal tokens
• In the Admin UI: Navigate to Settings → API Tokens

To create a team token:

• You must be a member of the team
• Verify your team membership in Admin UI → Teams

Issue 2 - "Unexpected token '<'"

This error means you're receiving HTML instead of JSON, typically caused by:

• Session/token expired → ICA receives login redirect page
• Incorrect API endpoint URL
• Network/proxy issues

Please verify:

1. Is ICA configured to use the correct ContextForge API URL?
2. Is your authentication token/session valid?
3. Are you specifically trying to create a team token or a personal token?

This appears to be an ICA configuration issue rather than a ContextForge bug. Please check ICA's connection settings and let us know if you need further assistance.

[crivetimihai]

You can work with @madhav165 if you need further help.