NOTE:
-
If you select an existing database connection in the connections dialog, the access level of the login to be used is shown in a tooltip.
-
Some user interfaces expect configuration user permissions at least. Logging in as an end user is not possible in this case.
To find the access level of the logged in user
-
To display user information, double-click the icon in the program status bar 
On the System user tab, in the SQL access level field, you will see the access level for the current login. The access levels displayed are End user, Configuration user, Administrative user, System administrator, and Unknown.
Related topics
Server and database permissions are predefined and cannot be modified.
NOTE: The End user role database role is permitted for custom schema extensions.
To display server and database permissions
-
In the Designer, select server role or the database role in the Base data > Security settings > Database server permissions > Database server login category.
This opens the List Editor showing a list of permissions.
The Redistributable STS (RSTS) is a Secure Token Server component service designed to provide user authentication using standard federation protocols such as WS-Federation and OAuth 2.0. One Identity Manager uses the RSTS for authentication to web applications with Webauthn and OAuth 2.0.
For more information about the Webauthn configuration, see the One Identity Manager Web Application Configuration Guide.
To install the RSTS
-
Launch autorun.exe from the root directory of the One Identity Manager installation medium.
-
Switch to the Other products tab
-
Select One Identity Redistributable STS and click Install.
-
On the start page of the installation wizard, click Next.
-
On the Select database page, select the One Identity Manager database connection. Select a user who has a minimum of administrative permissions for the database.
-
On the Installation settings page, enter the required information.
-
On the Installation page you can see the installation progress. When the installation has finished, click Next.
-
Click Finish to close the installation wizard.
Related topics
Due to security issues, you cannot run any database queries directly from the user interface or from web applications. Specific SQL operators undergo a risk assessment that prevents them from being used by One Identity Manager components. This includes operators such as LIKE, NOT LIKE, <, <=, >, or >=.
In order to continue using certain functions in One Identity Manager components, users require the Common_AllowRiskyWhereClauses program function.
Users who do not have this program function can only run database queries that are classified as trusted or pose no risk (risk index = 0.0). Some of the functions in One Identity Manager components, such as testing dynamic roles or running filter queries, are not possible without this function.
If you want to allow certain users to run security-critical queries, you can assign permissions to users through permission groups.
-
The QBM_Critical_WhereClause permissions group is provided for non role-based login. This group owns the program function. Add the system users who are allowed to run security-critical queries to the permissions group. Administrative system users automatically obtain these permissions groups.
-
The QER_4_Critical_WhereClause permissions group is provided for non role-based login. This group owns the program function. The permissions group is linked to the Base roles | security-critical queries application role. Add the system users who are allowed to run security-critical queries in the application role.
Using configuration parameters, you can also control the risk assessment of running the SQL statements.
NOTE: The configuration parameters are effective only for users who have the Common_AllowRiskyWhereClauses program function.
-
Use the QBM | SQLCheck | RiskEvaluation configuration parameter to define the risk assessment of running the SQL statements. Permitted values are:
-
Low: SQL statements with some risk are allowed.
-
Medium: The risk of SQL statements is assessed at a mitigated level. Thus, the threshold for blocking the user is reached later and more queries are possible.
-
Strict: The risk of SQL statements is assessed in full. However, the user is not blocked until a certain threshold is reached.
If the configuration parameter is not set, the risk assessment is performed with the value Strict.
-
Use the QBM | SQLCheck | SubSelect configuration parameter to specify how SQL statements with sub-queries are assessed. If the configuration parameter is set, then places where SQL statements with sub-queries are found are classified as higher risk.
Notes for customizations
-
As an example, database queries that are required on customized forms or database queries that are run over the application server API, must be formulated as predefined database queries in One Identity Manager. Database queries are always run with the permissions of the current user. For more information about using predefined database queries, see the One Identity Manager Configuration Guide.
-
You will find examples on the installation medium in the QBM\dvd\AddOn\ApiSamples directory.
-
For the alphabetical display of objects such as employees or company structures, you can use the QERVFirstUnicodeChar table in customized menus.
