Operations Readiness (B2C)

Status

You should ensure your operations staff knows how to monitor Login 3.0 service status and has set up a means to subscribe to updates on Login 3.0 status. All monitoring and notification setups for Login 3.0 must be coordinated with the UPBOND team.

The Login 3.0 status dashboard, along with any provided uptime dashboards, shows current and past status of the Login 3.0 service in a human-readable format. If any monitoring alerts are triggered, your operations staff should first check the status dashboard to see if there is a current outage. Regular checks with the UPBOND team ensure status monitoring is up-to-date.

Best Practice: Information on how to check the status of Login 3.0, as well as any dependent services (such as Social Providers), should be included in troubleshooting checklists for developers and helpdesk staff. Contact the UPBOND team to set up notification of status updates.

Email Provider Setup

You should verify with the UPBOND team that your email provider is configured to support production volumes of emails sent to customers for signup, email validation, account recovery, and other events. Customizations to email templates and advanced email handling must also be coordinated with the UPBOND team.

Best Practice: The default Login 3.0 email provider does not support production volumes or template customization. Set up a custom email provider through the UPBOND team before deploying to production.

Infrastructure

Firewalls

If custom code executing in Login 3.0 (e.g., Actions, Rules, Hooks, or Custom DB scripts) will call a service inside your network, coordinate with the UPBOND team to configure your firewall to allow inbound traffic from Login 3.0. The UPBOND team will manage region-specific IP addresses for firewall configuration.

NTP

Accurate system time is critical for authentication transactions. If your hosting environment doesn’t handle NTP (Network Time Protocol) automatically, ensure you work with the UPBOND team to monitor and manage NTP services.

Load Balancer Configuration

Ensure load balancer settings are correct, especially for features like sticky sessions or LDAP_HEARTBEAT_SECONDS, by coordinating with the UPBOND team. Misconfigurations can lead to intermittent errors.

Logs

UPBOND will manage logging configurations to ensure compliance with retention policies and advanced analytics. Login 3.0 logs are limited to a retention period of up to 30 days, depending on the subscription level, but exporting logs to external services for longer retention and analysis is highly recommended.

Best Practice: Use log streaming solutions managed by the UPBOND team to send log data to an external analytics service for advanced diagnostics and compliance.

Rate Limits and Other Errors

Login 3.0 provides error codes for rate limits and other issues. Automatic scanning of logs for rate limit errors must be set up with the UPBOND team to proactively address potential issues.

Best Practice: Avoid excessive API calls in Rules or Hooks by coordinating efficient configurations with the UPBOND team.

Monitoring

Set up proactive monitoring for Login 3.0 services with the help of the UPBOND team. This includes monitoring endpoints for service status and synthetic transaction monitoring for end-to-end authentication.

Best Practice: Coordinate with UPBOND to implement synthetic login transactions to monitor authentication pathways effectively.

Login 3.0 Notifications

Proactive Security Notifications and Operational Announcements

UPBOND team members will manage the receipt and monitoring of proactive notifications, including security updates and operational announcements.

Change Log

Review Login 3.0 change logs regularly for updates on features and breaking changes. The UPBOND team will provide guidance on implementing necessary changes.

Automated Deployment and Version Control

Automated deployment processes, including deployment automation for Login 3.0 tenants, must be configured by the UPBOND team. This ensures consistent configurations across environments and streamlined rollback processes.

Best Practice: Coordinate with UPBOND to unit test custom scripts and conduct integration tests prior to deployment.

By centralizing configurations and operations through the UPBOND team, you ensure a robust and compliant deployment of Login 3.0 for your production environment.