Operations (B2C)

Operationalization requires configuring or setting up infrastructure to support the scalable, measurable, and quantifiable operation that’s necessary for business continuity. In Login 3.0, this includes configuring supporting services (such as email providers), monitoring services for your deployment, detecting anomalous situations, and making preparations to recover quickly and smoothly when something goes wrong in a production environment. All configurations for operationalization must be requested and handled by the UPBOND team.

Establishing effective operational behaviors is something that successful customers have found pays dividends, and there are a number of things you will want to consider when looking at your workflow:

• What should you do to proactively detect failures?

• How can you obtain data on Login 3.0’s operational status?

• What should you do about Login 3.0 security bulletins related to the Login 3.0 service?

• Does Login 3.0 provide information regarding impending changes in the Login 3.0 service?

• How can you check for important notices from Login 3.0?

• What should you do with Login 3.0 log data so that you can analyze it and keep it for longer than Login 3.0’s limited data retention period?

• How can you scan Login 3.0 logs to determine if peak loads in your application trigger any rate limits or other errors?

• What email services should you use to support production volumes of email messages to users?

Email Provider Setup

Login 3.0 sends emails to users for events such as signup welcome, email validation, breached password, and password reset events. You can customize the email templates for each type of event. Login 3.0 provides a test email provider with limited capacity for basic testing, but you must set up your own email provider for production use. All configurations for email providers must be requested from the UPBOND team.

Best Practice

The default Login 3.0 email provider does not support sending production volumes of email or customization of email templates. You should therefore configure your own email provider before deploying to production.

Infrastructure

Firewalls

If custom code executing in Login 3.0 will call a service inside your network, or if you configure an on-premise SMTP provider in Login 3.0, then you may need to configure your firewall to allow inbound traffic. All firewall configurations and necessary IP allowlisting must be handled by the UPBOND team.

Logging

Login 3.0 provides extensive capability when it comes to the logging of events, and also in the scanning of logs in order to identify event anomalies. Standard log retention period for Login 3.0 logs is determined by subscription level, with the shortest period being 2 days and the longest period being only 30 days. All configurations for log streaming or integration with external logging services must be requested from the UPBOND team.

Best Practice

You should leverage one of the log streaming solutions to send log data to an external log analytics service. This will enable keeping data for longer periods of time and provide advanced analytics on the log data.

Rate Limits and Other Errors

Login 3.0 provides a unique error code for errors reported when the rate limit is exceeded. You should set up automatic scanning of logs to check for rate limit errors so you can proactively address activity that hits rate limits before it causes too much trouble for your users. All configurations related to rate limit handling must be managed by the UPBOND team.

Monitoring

You should establish mechanisms for monitoring Login 3.0 implementations so your support or operations team receives the timely information needed to proactively handle service outages. All monitoring endpoints and configurations for synthetic transaction monitoring must be set up by the UPBOND team.

Notifications

Security Bulletins

Login 3.0 regularly conducts security-related tests and proactively identifies and notifies customers who need to make security-related changes. All notifications regarding security bulletins and changes must be handled by the UPBOND team.

Service Status

The Login 3.0 status and uptime dashboards show the current and past status of the Login 3.0 service in a human-readable format. Any monitoring alerts or subscriptions to outage notifications must be configured by the UPBOND team.

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 part of a troubleshooting checklist for developers and helpdesk staff. Subscribe to notifications to stay informed. All service status configurations must be requested from the UPBOND team.

In the event of an outage, Login 3.0 performs a Root Cause Analysis (RCA) and publishes the results. This document includes root cause, contributing factors, and prevention measures, and can take a few weeks to be published.