# Test Application Locally

While authenticating users through Login 3.0 generally requires an internet connection, local development and testing are supported in specific scenarios. Follow these guidelines to effectively test applications using Login 3.0 in a local environment.

***

### **Testing Sessions with Server-Side Applications**

For server-side applications, you may need to manually log in through Login 3.0 to generate valid sessions for testing.

#### Steps:

1. **Use the Authorization Code Flow:**

   Test the flow locally by configuring your application to authenticate users via this secure mechanism.
2. **UPBOND Team Support:**

   Request the UPBOND team to assist with any configurations required for local testing, such as adding local callback URLs.

***

### **Configuring Local Domains**

When developing locally, you can use `localhost` or intranet domains as callback URLs during testing. For example, you might configure `http://localhost:3000/callback` as your callback URL.

#### Steps:

1. **Provide Callback URL to UPBOND:**

   Share your local development callback URL with the UPBOND team.
2. **Configuration by UPBOND:**

   The team will add the URL to your application's **Allowed Callback URLs** list.
3. **Testing Redirects:**

   Login 3.0 redirects users to your callback URL with required information in a query string or hash fragment. Ensure your application correctly handles these redirects.

***

### **Divert Emails for Testing**

If your application sends emails during user creation, validation, or password reset processes, you can divert these emails during testing to prevent actual delivery.

#### Important Notes:

* **Avoid False Domains:**

  Login 3.0 does not support "false" domains commonly used for testing. Use real email addresses to avoid errors.
* **UPBOND Assistance:**

  Request the UPBOND team to configure your test email provider for the application.
