Support for JWS Tokens as a Dedicated Entry Type in Devolutions Server

Description:
Currently, Devolutions Server supports various credential and authentication storage methods, including password entries, API keys, and secure notes. However, there is no dedicated support for JSON Web Signature (JWS) tokens. JWS tokens are widely used for secure authentication and authorization, particularly in machine-to-machine (M2M) communication and modern API-driven environments.

Suggestion:
I propose adding a dedicated entry type for JWS tokens, allowing users to securely store, manage, and track these tokens within Devolutions Server. The new entry type should include:

• Secure storage for the token value
• Optional fields for metadata such as expiration date, issuer, and audience
• Automatic validation and integrity checks for stored tokens

Benefits:

• Improved Security: Ensures that JWS tokens are stored securely with controlled access, reducing the risk of leakage or misuse.
• Better Organization: Provides a structured way to manage JWS tokens instead of relying on generic secure notes or custom fields.
• Automation & Integration: Enables users to programmatically retrieve and rotate tokens, enhancing automation capabilities within secure environments.
• Compliance & Auditing: Allows tracking of JWS token usage, supporting compliance with security best practices and regulatory requirements.

This feature would be valuable for organizations leveraging Devolutions Server to manage secure authentication credentials, particularly in DevOps and enterprise IT environments. Thank you for considering this request!