Understanding Security Tokens in Micromine Geobank Data Views.

Summary: This article explains the concept of security tokens in Micromine Geobank data views, providing row-level security at the application level.

What are Security Tokens?
In Micromine Geobank, security tokens control access to data at the row level. They provide basic support for row-level security (RLS) and can be used to restrict the editing or deletion of rows based on certain conditions.

How Security Tokens Work:

1. Security Token Values and Meanings: The following table outlines the binary values, corresponding integer values, and meanings of security tokens.
   
   

   Binary	Value	Meaning
   000	0	Read-only
   001	1	Insert only
   010	2	Delete only
   011	3	Delete/Insert only
   100	4	Update only
   101	5	Update/Insert
   110	6	Update/Delete
   111	7	Update/Delete/Insert

   
   
   
2. Token Assignment:  Identify the column containing the security token in the data view. Access column properties to view or modify the security token. Token values can be assigned to a column using the "Treat as Security Token" option.
   
   
   
   
3. Row-Level Control: When an operator views or edits rows with security tokens, they can only access those rows based on their token value.

Security Token Examples:

1. Date Updated Token: A query can return a date-based security token that changes daily. For example:
   • If the last updated date is greater than one day from the current date, the token is 0 (Read-only).
   • If it's less than or equal to one day from the current date, the token is 7 (Update/Delete/Insert).
2. Substitution Parameters-based Token: A custom security token can be created using a Substitution Parameter in the Geobank data view.
   • It could be, for example, a password that allows the data view to be editable (or even down to a specific frame/grid to be or not possible to edit)

Tip: It would be helpful to make this Security Token field not editable and not visible on the grid.

Security Token Properties:

1. Column Property: Security tokens are identified in the column properties.
2. Token Value Range: The range of values for each token is determined by the value (e.g., 0-7).
3. Operator Access: Operators can only access rows with security tokens that match their token value.

Please be aware that it is not possible to edit, delete, or insert a new row for rows with a SECURITY_TOKEN value of 0.

Limitations:

1. Basic Security: Micromine Geobank's built-in security features are basic and may not provide comprehensive row-level control.
2. Application-Level Only: Security tokens apply at the application level, not the database level (i.e., triggers).

By using security tokens in Micromine Geobank, you can implement a simple yet effective way to restrict access to data based on specific conditions or user roles.

Want to learn more?

Online Help Manuals - Click here for the latest version

Learning Management System - Click here to login or here to request access