Authentication Service Add-on Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Release 5.14.0.2303¶
Released March 20, 2025
The Authentication Service now supports integration with HashiCorp Vault. (AL-180791)
Release 5.14.0.2249¶
Released January 23, 2025
We fixed a bug that could cause metadata extraction (MDE) to fail for the AWS Glue OCF connector after the Alation instance is restarted. (AL-180578)
Release 5.14.0.2221¶
Released November 21, 2024
We have patched some dependencies to address security vulnerabilities. (AL-174562)
Release 5.14.0.2169¶
Released September 25, 2024
The Authentication Service add-on logs will now include:
The
tenantid
of the Alation instance that the Alation Agent is connected to.The
agentid
of the Alation Agent that is running the Authentication Service add-on.
(AL-169979)
Release 5.14.0.2058¶
Released August 28, 2024
We have updated the format of the Authentication Service add-on logs to make them easier to parse and more consistent with the format of other Alation logs.
The structure of the header
section is always the same. The following fields are included in the header
section for consistency with other Alation components but are not used by the Authentication Service add-on:
The
instanceurl
field is not used and is always empty.The
tenantid
field is not used and is always set toFAKE_TENANT_ID
.
The structure of the data
section depends on the message.
Example log message:
{
"header": {
"appname": "authservice",
"instanceurl": "",
"loglevel": "INFO",
"tenantid": "FAKE_TENANT_ID",
"timestamp": "2024-08-12T16:51:15.987Z"
},
"data": {
"msg": "Reading all the configurations for a plugin: aws_scm",
"logger": {
"name": "alation.authserver.configuration.ConfigManager",
"fqcn": "org.apache.log4j.Category"
},
"thread": {
"name": "grpc-default-executor-0",
"id": 16,
"priority": 5
},
"source": {
"className": "alation.authserver.configuration.ConfigManager",
"fileName": "ConfigManager.java",
"methodName": "readAll",
"lineNumber": 233
}
}
}
(AL-120676)
Release 5.14.0.1968¶
Released July 25, 2024
The Authentication Service add-on now offers the ability to connect to AWS Secrets Manager using IAM user credentials. This allows you to use the Authentication Service add-on in non-AWS environments. To use this feature, you must be an Alation Cloud Service customer on the cloud-native architecture who has upgraded to Alation 2024.1.5. See Integrate Agent with Secrets Manager Using IAM User Credentials for more information.
Release 5.14.0.1882¶
Released July 16, 2024
This is the initial release of the Authentication Service add-on for the Alation Agent. In the initial release, integrating with AWS Secrets Manager using an IAM instance profile is supported. To use this feature, you must be an Alation Cloud Service customer on the cloud-native architecture who has upgraded to Alation 2024.1.4. See Integrate Agent with Secrets Manager Using IAM Instance Profile for more information.
Note
The Authentication Service add-on has been used internally in Alation Cloud Service itself for some time now. That’s why the version number for the initial external release is already so high.