Authentication & Security
Enhanced /api/security/ OPTIONS for authentication method management
We’ve enhanced the /api/security/ OPTIONS response to provide greater visibility and control over authentication configuration.
With this update, the response now includes detailed information about the authentication_method field, enabling you to programmatically understand and configure allowed login methods for different user types.
This improvement makes it easier to build more flexible and secure authentication workflows, while reducing the need for manual configuration or guesswork when integrating with the API.
Example response structure
{
"details": {
"schema": [
{
"alias": "password_complexity",
"schema": [
{
"alias": "max_repeating_chars",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
},
{
"alias": "min_letters",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
},
{
"alias": "min_numbers",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
},
{
"alias": "min_symbols",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
},
{
"alias": "min_lower_case",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
},
{
"alias": "min_upper_case",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
},
{
"alias": "min_length",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
}
]
},
{
"alias": "systemconf",
"schema": [
{
"alias": "password_prevent_reuse",
"type": "bool",
"required": false
},
{
"alias": "password_rotation_interval",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 },
{ "type": "max_value", "value": 32767 }
]
},
{
"alias": "activation_link_valid_period",
"type": "int",
"required": false,
"validators": [
{ "type": "min_value", "value": 0 }
]
}
]
},
{
"alias": "authentication_method",
"schema": [
{
"alias": "internal",
"type": "enum",
"required": false,
"values": [
{ "value": "any", "text": "Any" },
{ "value": "password", "text": "Password" },
{ "value": "sso", "text": "Single Sign-On" }
]
},
{
"alias": "external",
"type": "enum",
"required": false,
"values": [
{ "value": "any", "text": "Any" },
{ "value": "password", "text": "Password" },
{ "value": "sso", "text": "Single Sign-On" }
]
},
{
"alias": "full",
"type": "enum",
"required": false,
"values": [
{ "value": "any", "text": "Any" },
{ "value": "password", "text": "Password" },
{ "value": "sso", "text": "Single Sign-On" }
]
},
{
"alias": "super_admin",
"type": "enum",
"required": false,
"values": [
{ "value": "any", "text": "Any" },
{ "value": "password", "text": "Password" },
{ "value": "sso", "text": "Single Sign-On" }
]
}
]
}
]
}
}Updated authentication expiry notifications
We’ve refreshed the Authentication Object expiry notification emails to make them clearer, more consistent, and easier to act on.
The updated template now applies to both upcoming expiries and already expired Authentication Objects, providing a more unified and streamlined experience.
Updated email content
Title: Action needed: status update for your Authentication Object
Dear <name>,
We’re contacting you regarding the status of one of your Authentication Objects. Our system indicates that it is either approaching its expiry date or has already expired.
Details :
• Authentication Object : <name>
• Provider : <provider>
• ID : <id>
• Link: <link>
• Expiry Date : <datedime>
• Applies To : <parameter>
To ensure uninterrupted access and workflow continuity, please review this Authentication Object and update it if it is still required.
If the Authentication Object is no longer in use, you may safely ignore this message.
<email admin signature>As part of this update, we’ve also simplified the expiry date format by removing the time element - making key information clearer and easier to understand at a glance.