A private connection profile allows an administrator to configure the database connection while keeping user credentials separate.
Creating a private connection follows the standard Connection Profile Wizard. The primary difference is selecting Is Connection Private?
Screenshots use fictional demo data consistent with the other WebReports articles.
Why use a private connection?
Use a private connection when users need to connect with their own database username and password instead of sharing one database login.
An administrator configures the connection profile, while each user supplies their credentials separately. This lets users reuse the configured connection settings while keeping their database sign-ins separate. It is useful when users already have individual database accounts or need to maintain their own database credentials.
Demo example: An administrator creates the DemoArchive connection profile. Alex Johnson and Amanda Lee can use that profile with their own database usernames and passwords, rather than sharing one set of credentials.
Open the Connections page
- Sign in to WebReports.
- Select Management.
- Select Connections.
Create a private connection profile
- Select Add.
- Enter a unique connection profile name.
- Select Is Connection Private?
- Select the applicable connection type.
- If required by your environment, select Prefix TO/Schema Name.
- Select Next.
- Complete the remaining connection settings required for the selected connection type.
- Select Finish to save the connection profile.
Verify the private connection
After saving the connection profile, return to the Connections page.
Locate the new connection and verify that the Is Priv. column identifies it as a private connection.
Private-connection credentials are managed separately and are not covered in this article.
Comments
0 comments
Please sign in to leave a comment.