Yes, an access profile can be acknowledged during certifications. During access certification campaigns, reviewers can review access profiles as part of the items that need to be certified. They can either approve or revoke access to the access profiles, just like they would with individual entitlements. This ensures that users' access to these bundled entitlements is regularly reviewed and compliant with organizational policies.
References:
* SailPoint IdentityNow Certification Campaigns Guide.
* SailPoint IdentityNow Access Profile Certification Documentation.

Yes, SailPoint IdentityNow APIs can be accessed and utilized by external clients such as cURL or Postman.
These tools are commonly used for testing and interacting with RESTful APIs, and they work seamlessly with IdentityNow's API framework. For example, developers can use Postman or cURL to make API calls for various actions like managing identities, querying data, and triggering provisioning events.
Key Reference from SailPoint Documentation:
* API Integration with Tools: SailPoint IdentityNow supports third-party tools like cURL and Postman for API interaction, as these clients can handle HTTP requests, which is how IdentityNow's APIs communicate.

Turning off the Virtual Appliance's (VA) internal firewall is not recommended as a standard troubleshooting step in SailPoint IdentityNow. The VA's firewall is crucial for maintaining the security of the environment, and disabling it can expose the system to unnecessary risks. Instead, an IdentityNow engineer should verify the VA's network configuration and ensure that the required ports are open for communication between the VA and the source.
Key Reference from SailPoint Documentation:
* VA Configuration and Network Troubleshooting: Troubleshooting connection issues typically involves checking network connectivity and firewall rules, not turning off the internal firewall.

In SailPoint IdentityNow, provisioning is the process of granting or revoking access to systems and applications based on access requests or changes in user identity attributes. The scenario describes John Doe requesting access to the "Sales" profile in Salesforce, which is approved by his manager.
However, simply approving an access request does not automatically trigger provisioning unless specific conditions are met:
* Provisioning Policy: For the access to be provisioned, SailPoint IdentityNow requires a provisioning policy that defines the action to be taken after the approval process. This policy is often configured to specify whether access should be granted or denied after approval. If no provisioning policy is linked to the requested access, no action will be triggered.
* Source Configuration: The Salesforce source (connector) in SailPoint IdentityNow must also be properly configured to handle provisioning tasks. Without proper configuration of the Salesforce source, no provisioning action will be sent even if the request is approved.
* Manual Provisioning Workflow: In some cases, IdentityNow might be configured to require manual intervention after approval (e.g., triggering a manual provisioning workflow or an additional step) to enforce the provisioning action. If this configuration is missing, the approved request will not lead to automatic provisioning.
Since the scenario does not explicitly state that a provisioning policy or source configuration exists to handle the access request, the correct conclusion is that no provisioning would be sent out.
Key Reference from SailPoint Documentation:
* Provisioning Concepts in IdentityNow: Documentation emphasizes that provisioning is triggered by defined workflows and provisioning policies that link the request to the connector source. Without these, the approval does not lead to actual provisioning.

Clearing the authentication checkbox for a source in SailPoint IdentityNow is not a typical troubleshooting step for a timeout error. This option is related to whether or not authentication is required for the source connection. A timeout error typically points to a network issue (e.g., port, firewall, or network latency), not authentication problems. The engineer should instead focus on network-related configurations such as checking port access or firewall settings.
Key Reference from SailPoint Documentation:
* Source Connectivity Troubleshooting: Timeout errors are generally caused by network issues rather than authentication problems, so adjusting authentication settings is not recommended for resolving such errors.