Applications in Login 3.0

In Login 3.0, the term application refers to any software integrating authentication and authorization functionality. This can include:

• Single-page applications (SPAs) operating in a browser.

• Regular web applications running on servers.

• Machine-to-machine (M2M) applications interacting with APIs.

Applications are categorized based on their characteristics and setup requirements.

---

Application Types

To add authentication to your application, you must request the UPBOND team to register it. Login 3.0 supports the following application types:

• Single-Page Application (SPA):

  JavaScript-based browser apps (e.g., React, Angular) where UI logic runs client-side and APIs are used for server communication.

  To set up, refer to Register Single-Page Web Applications.

• Native Application:

  Apps running natively on mobile or desktop platforms (e.g., iOS, Android).

  To set up, refer to Register Native Applications.

• Machine-to-Machine (M2M) Application:

  Non-interactive apps like IoT devices, daemons, or backend services requiring API access.

  To set up, refer to Register Machine-to-Machine Applications.

---

Credential Security

According to OAuth 2.0 standards, applications are classified as:

• Confidential Applications:

  Capable of securely storing credentials (e.g., server-side applications).

• Public Applications:

  Unable to securely store credentials (e.g., SPAs, mobile apps).

  For more information, consult the UPBOND team.

---

Ownership

Applications are categorized by ownership:

• First-Party Applications:

  Owned and controlled by the organization managing the Login 3.0 tenant.

• Third-Party Applications:

  Developed by external parties, allowing secure access to APIs. Contact the UPBOND team for assistance with third-party application setup.

---

Manage Applications

All application registrations and configurations must be requested through the UPBOND team. Available management features include:

• Customizing login flows for different applications.

• Configuring multi-tenant environments to meet specific use cases.Refer to Multi-Tenant Application Best Practices for guidance.

By default, Login 3.0 enables all tenant-associated connections for newly created applications. If specific connections need to be enabled or disabled, inform the UPBOND team.

---

Monitor Applications

Login 3.0 logs various events, such as:

• Successful and failed user authentications.

• Password reset requests.

• Administrative actions.

Log data can be exported and integrated with third-party tools like Sumo Logic, Splunk, or Mixpanel for detailed analysis. Contact the UPBOND team to configure log exports.

---

Remove Applications

Applications can be removed by requesting the UPBOND team to delete them. Ensure all dependencies and integrations are updated accordingly.

---

Manage Client Secrets

Client secrets are essential for securing applications. They:

• Ensure tokens are issued only to authorized applications.

• Must not be included in public-facing apps like mobile or browser-based applications.

If a client secret is compromised, contact the UPBOND team immediately to rotate to a new secret and update all associated applications.

---

Grant Types

Login 3.0 supports various OAuth 2.0 grant types for authentication and authorization. During registration, specify the appropriate grant types to the UPBOND team. These configurations will be applied during the application setup process.