App Registration

Register a new application in the rNet developer dashboard to obtain your Client ID, Client Secret, and configure your redirect URI.

Register a New Application

1

Open the Registration Form

From the Dashboard, click the + New button in the Applications section, or use the Register New Application form on the right side of the dashboard.
2

Enter Application Details

Fill in the required fields:
  • Application Name: A human-readable name displayed to users during authorization (e.g., "My AI Chat App").
  • Redirect URI: The exact URL where rNet will send users after authentication. See Callback Configuration below.
3

Click Register Application

Submit the form. rNet will generate a unique Client ID and Client Secret for your application.

Registration Form

Application registration form showing Application Name and Redirect URI fields
4

Copy Your Credentials

After successful registration, you'll see your Client ID and Client Secret. Copy the secret immediately. It will not be shown again.

Registration Success

Successful registration screen showing Client ID and Client Secret
Save Your Client Secret
The Client Secret is displayed only once. Copy it immediately and store it in your backend environment variables. If you lose it, you'll need to regenerate credentials.
5

Store Credentials in Your Backend

Add the credentials to your backend environment file. Never expose these in frontend code or commit them to version control.
bash
RNET_CLIENT_ID=rnet-xxxxxxxx
RNET_CLIENT_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Callback Configuration

The Callback URL (also called Redirect URI) is the URL where rNet redirects the user after they authenticate. When login succeeds, rNet appends an authorization code parameter to this URL and sends the user's browser there.

Why It Must Match Exactly

The redirect URI you pass during the login request must exactly match the one registered in your dashboard, including the protocol, domain, port, path, and trailing slashes. Any mismatch will cause the authorization to fail with an error.

Allowed Formats

Valid Examples

  • https://myapp.com/api/auth/callback
  • https://api.myapp.com/v1/oauth/rnet
  • http://localhost:3000/callback (dev only)
  • http://localhost:3001/auth/rnet (dev only)

Invalid Examples

  • http://myapp.com/callback (no HTTPS in prod)
  • https://myapp.com (missing path)
  • 192.168.1.5/callback (raw IP address)
  • https://myapp.com/callback/ (trailing slash mismatch)
Next
With your app registered and callback configured, learn how users authenticate in User Authentication.

Quick Reference Links