Clarification on REST API token generation with READ and WRITE authorities (Issue #2355)

[shubh1978]

Hi SW360 maintainers and community,

While setting up SW360 locally and reproducing Issue #2355, I verified the REST API token generation workflow.

Summary

I was able to successfully generate REST API tokens with both READ and WRITE authorities using the default setup and official installation instructions.

The behavior appears to work correctly when:

• SW360 backend is running properly
• CouchDB is configured and accessible
• User authentication is working correctly
• Token is generated via Preferences → REST API Token

What I observed

• Token generation works as expected
• READ and WRITE authorities are correctly included
• No additional configuration changes were required

Contribution

To help clarify this behavior and avoid confusion for future developers, I submitted a documentation PR:

#3691

Request for feedback

Could maintainers please confirm:

• Whether the current behavior is expected
• Or if there are specific environments where the issue still occurs

Tagging maintainers for visibility:

@amritkv
@GMishx
@KoukiHama
@ag4ums
@arunazhakesan

Thank you for maintaining SW360 and supporting contributors.