First-Time Setup
Configure Licentra Settings
After installing the Licentra bundle, configure the connection between your NetSuite instance and the Licentra license management platform.
Configuration Overview
This process involves two main steps:
- Create Licentra Config Record - Store connection settings
- Create API Secret - Store authentication credentials
Step 1: Create Licentra Config Record
The Licentra Config record stores the primary connection settings for your NetSuite instance.
Access Configuration
- Navigate to:
Setup > Company > Licentra Config - Click "New Licentra Config" to create a new configuration record
Required Configuration Fields
| Field | Description | Value | Notes |
|---|---|---|---|
| License Server URL | Licentra API server URL | https://beta.licentra.api.bringitproducts.com | Use development URL for sandbox |
| Client Id | Unique identifier for your NetSuite client | From Licentra portal | Required field |
| Client Secret Reference | Internal ID of API Secret record | From API Secret creation | Required field |
| Signature Type | Cryptographic algorithm for API requests | HS256 | Recommended default |
Environment-Specific URLs
Choose the appropriate License Server URL based on your environment:
- Development/Sandbox:
https://beta.licentra.api.bringitproducts.com
Important: Save the Licentra Config record after filling in all required details.
Step 2: Create API Secret
The API Secret stores the confidential "License Secret" for secure communication with Licentra.
Access API Secrets
- Navigate to:
Setup > Company > API Secrets - Click "Create New" to create a new API Secret
Configure Secret Details
| Field | Description | Example Value | Notes |
|---|---|---|---|
| Name | Descriptive name for your secret | Licentra Integration Secret | Make it memorable |
| ID | Internal ID for Client Secret Reference | licentra_api_secret | Use this in Config record |
| Password | License Secret from Licentra subscription | Highly sensitive credential | Copy exactly from portal |
| Description | Optional context | API Secret for Licentra License Manager Integration | Helpful for future reference |
| Restrictions | Access permissions | ✅ Check "Allow for all Scripts" | Required for Licentra scripts |
Security Best Practices
- Store the License Secret securely - Never share it publicly
- Use a descriptive name - Makes it easier to identify later
- Document the ID - You'll need it for the Config record
- Enable script access - Required for Licentra functionality
Step 3: Link Config and Secret
After creating both records:
- Return to the Licentra Config record
- Enter the API Secret ID in the "Client Secret Reference" field
- Save the configuration again
Step 4: Validate Configuration
Use the License Viewer to confirm your configuration is working correctly.
Access License Viewer
- Navigate to:
Setup > Company > Licentra License Viewer - Wait for the page to load completely
Verify Successful Connection
Successful Configuration Indicators:
- Sublist appears displaying all subscriptions and features
- Available licenses are visible and accessible
- Connection status shows as active
- No error messages displayed
Troubleshooting Connection Issues
If the sublist is empty or no data appears:
- Click "Refresh Token from Server" link
- Check for error messages below the link
- Common issues and solutions:
| Issue | Possible Cause | Solution |
|---|---|---|
| Empty sublist | Incorrect Client ID | Verify Client ID in Licentra portal |
| Connection timeout | Invalid API Secret | Check License Secret in API Secret record |
| Server error | Wrong License Server URL | Confirm URL for your environment |
| Permission error | API Secret not accessible | Verify "Allow for all Scripts" is checked |
Step 5: Test License Enforcement
After successful configuration:
- Access a licensed module in NetSuite
- Verify license validation is working
- Check license usage in the License Viewer
- Test license restrictions if applicable
Configuration Checklist
Before proceeding, verify all items are complete:
- Licentra Config record created with correct URL
- Client ID entered correctly
- API Secret created with License Secret
- Client Secret Reference linked to Config record
- License Viewer shows subscriptions and features
- No error messages in License Viewer
- License enforcement working correctly
Advanced Configuration
Custom Signature Types
For now only HS256 is recommended
Multiple Environments
For organizations with multiple NetSuite instances:
- Create separate Config records for each environment
- Use environment-specific URLs and credentials
- Test each environment independently
Getting Help
If you encounter configuration issues:
- Review the troubleshooting guides for common solutions
- Check error messages in the License Viewer
- Verify all field values are correct
- Contact your Licentra administrator for credential issues
- Reach out to BringIT support for technical assistance
Next Steps
After successful configuration:
- Review Configuration Reference - Understand all available settings
- Monitor License Usage - Track license consumption
- Set Up User Training - Train your team on using the integrated system
Last modified on