When you click a link to log in using single sign-on (SSO), you now have the option
to log in using a user name and password or your organization ID.
Previously, the organization ID was required to log in using SSO.
The initial login still requires an organization ID, but
the administrator can add users to the appropriate user groups through the SAML
configuration in Administrator to enable user name and password even with the
initial login.
Serverless runtime environments in AWS
For serverless runtime environments on AWS, you must manually create and configure
AWS resources in your VPC.
Previously, Informatica provided an AWS CloudFormation template for you to create a
serverless runtime environment.
For more information about serverless runtime environments, see
Runtime
Environments
.
Using the agent REST API resource
to get Secure Agent service status
When you use the agent REST API resource to request details about the services that
run on your organization's Secure Agents, the response includes the
agentEngineStatus object by default.
If you want the response to also include the agentEngineConfigs object, add
?onlyStatus=false
to the request. For example, the following
request returns the agentEngineStatus and agentEngineConfigs objects for the
specified Secure Agent:
GET /runtime/api/v2/agent/details/<agent ID>?onlyStatus=false
Previously, the response included the agentEngineStatus and agentEngineConfigs
objects by default.
For more information about the agent resource, see