OpenText Identity and Access Management - OpenText Push Notifications for Cloud Messaging Integration and Automation

Common Integration Use Cases Between OpenText Identity and Access Management and OpenText Push Notifications for Cloud Messaging

1. Secure approval notifications for access requests

When a user requests access to a protected OpenText application or role, OpenText Identity and Access Management can trigger a push notification through OpenText Push Notifications for Cloud Messaging to the approver?s mobile or web device. The approver receives a real-time alert with request details and can review and act quickly.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Faster access approvals, reduced delays for employees and contractors, improved audit responsiveness
• Typical users: Security administrators, application owners, department managers

2. Multi-factor authentication and login verification alerts

OpenText Identity and Access Management can use push notifications to support login verification for sensitive access events, such as first-time sign-in, password reset, or access from an unusual device or location. Users receive a notification prompting them to confirm or deny the action.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Stronger authentication, lower account takeover risk, better user experience than manual code entry in some scenarios
• Typical users: Employees, partners, administrators

3. Real-time alerts for privileged account activity

When privileged roles are assigned, elevated, or used, OpenText Identity and Access Management can send immediate push alerts to security teams or account owners. This helps teams detect unexpected privilege changes and respond before misuse escalates.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Faster detection of risky access changes, improved governance, reduced exposure from privileged accounts
• Typical users: Security operations, identity governance teams, compliance teams

4. User notification for access policy changes and required actions

When access policies change, such as password expiration, role recertification, or mandatory reauthentication, OpenText Identity and Access Management can notify affected users through push messages. This ensures users complete required actions before access is interrupted.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Higher policy compliance, fewer help desk tickets, less downtime caused by expired credentials or missed reviews
• Typical users: End users, managers, compliance coordinators

5. Session and account risk notifications to end users

If OpenText Identity and Access Management detects suspicious behavior, such as repeated failed logins, account lockout, or access from a new region, it can send a push notification to the user asking them to confirm activity or contact support. This creates a fast feedback loop for potential security incidents.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Faster incident response, reduced fraud risk, improved user awareness of account security events
• Typical users: End users, service desk, security analysts

6. Mobile access enrollment and onboarding guidance

During onboarding, OpenText Identity and Access Management can trigger push notifications that guide new users through account setup, SSO enrollment, and policy acceptance. This is especially useful for mobile-first or distributed workforces that need step-by-step prompts.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Faster onboarding, fewer setup errors, reduced support burden for new user provisioning
• Typical users: New hires, HR onboarding teams, IT support

7. Administrative alerts for identity workflow exceptions

When identity workflows fail, stall, or require manual intervention, OpenText Identity and Access Management can send push notifications to administrators or workflow owners. Examples include failed provisioning, incomplete approvals, or synchronization issues with enterprise identity providers.

• Data flow: OpenText Identity and Access Management to OpenText Push Notifications for Cloud Messaging
• Business value: Shorter resolution times, fewer broken access processes, better operational visibility
• Typical users: IAM administrators, integration support teams, service desk leads

8. Bi-directional user preference and notification control for secure communications

OpenText Identity and Access Management can manage user identity attributes and notification preferences, while OpenText Push Notifications for Cloud Messaging delivers messages based on those preferences and access context. This allows organizations to control who receives which alerts, on which devices, and under what conditions.

• Data flow: Bi-directional between OpenText Identity and Access Management and OpenText Push Notifications for Cloud Messaging
• Business value: Better governance over notification delivery, reduced noise, improved relevance of security and workflow alerts
• Typical users: Identity administrators, compliance teams, business users