Source Credentials and Access
Overview
Once source connectivity has been validated, the next step is to ensure that visability systems can successfully authenticate and access each source.
Many sources require credentials to retrieve content. Even when network access is available, missing or incorrect credentials will prevent sources from being configured or displayed.
ADD NOTES ON APP SERVER AND PERSISTING AUTHENTICATION
Why Credentials Matter
visability may need to authenticate to a source before it can retrieve content. This applies to a wide range of source types, including:
- Camera or VMS streams
- Web-based dashboards and applications
- Encoder or third-party systems
- Secured APIs or data services
If authentication fails, the source may appear unavailable or fail to load entirely.
What Needs to Be Confirmed
For any source that requires authentication, the following should be defined ahead of time:
- Username and password (or other required credentials)
- Any domain or system context required for login
- Access level needed to retrieve the content
Credentials should be validated to ensure they are correct and actively working.
Testing Access
Where possible, credentials should be tested prior to commissioning.
This may include:
- Logging into a web application or dashboard
- Accessing a secured stream or endpoint
- Verifying permissions within a VMS or third-party system
Testing helps confirm that credentials are not only correct, but also have the appropriate level of access.
Managing Credentials
To ensure long-term reliability, it is important to consider how credentials are managed.
- Avoid using personal user accounts where possible
- Use dedicated or service-based accounts when appropriate
- Be aware of password expiration policies
- Ensure credentials are available to the deployment team when needed
Failure to account for credential management can lead to unexpected access issues after deployment.
Common Issues to Avoid
- Missing credentials at the time of commissioning
- Incorrect usernames or passwords
- Accounts lacking sufficient permissions
- Expired or locked accounts
- Relying on individual user accounts that may change over time