Application
The application entity usually represents web applications whose users are administrated in nevisIDM.
nevisIDM itself is also administrated as an application.
When nevisIDM runs in multi-client mode, applications need explicitly to be assigned to clients to be available to users of those clients. The assignment is stored in the table TIDMA_CLIENT_APPLICATION shown below.
Database table TIDMA_APPLICATION
| DB attribute | Java data type (max. size), defaults | Description |
|---|---|---|
| application_id | Long, not NULL | Primary key (uniquely identifies each individual DB entry) |
| description | String(1000), nullable | |
| displayed | Boolean, not NULL | Flag which defines if an application will be displayed on a portal |
| displayname_dict_entry_id | Long, nullable | Field links to the application's name in other languagesForeign key that links to information in the table TIDMA_DICT_ENTRY |
| extid | String(50), not NULL | External identifier |
| name | String(100), not NULL | The application's technical name. It has to be unique and will be propagated in the security token to other systems. |
| url | String(1000), nullable | URL of web applications |
Database table TIDMA_CLIENT_APPLICATION
| DB attribute | Java data type (max. size), defaults | Description |
|---|---|---|
| application_id | Long, not NULL | Foreign key that links to information in the table TIDMA_APPLICATION |
| client_application_id | Long, not NULL | Primary key (uniquely identifies each individual DB entry) |
| client_id | Long, not NULL | Foreign key that links to information in the table TIDMA_CLIENT |