Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:server:security:manager [2018/02/02 08:20] admin |
jvx:server:security:manager [2020/07/22 13:07] (current) cduncan errant comma |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~Title: Implementing the Security Manager~~ | ~~Title: Implementing the Security Manager~~ | ||
| - | The security manager is used when the client or a user have to be authenticated. In this case the login data will be transmitted by the client to the server for verification. The server will always delegate the verification of login data to a defined security manager. | + | The security manager is used when the client or a user has to be authenticated. In this case, the login data will be transmitted by the client to the server for verification. The server will always delegate the verification of login data to a defined security manager. |
| - | After successful verification the client can complete the login process. In the case of an error a detailed error message will be shown. | + | After successful verification, the client can complete the login process. In the case of an error, a detailed error message will be shown. |
| Our goal is the implementation and use of a security manager. The valid user/password combinations are shown in a hash table. | Our goal is the implementation and use of a security manager. The valid user/password combinations are shown in a hash table. | ||
| - | == Implementing the security manager == | + | == Implementing the Security Manager == |
| Create the server class ''apps.firstapp.security.HashtableSecurityManager'' and implement the interface ''com.sibvisions.rad.server.security.ISecurityManager''. For example: | Create the server class ''apps.firstapp.security.HashtableSecurityManager'' and implement the interface ''com.sibvisions.rad.server.security.ISecurityManager''. For example: | ||
| Line 168: | Line 168: | ||
| ''changePassword'' allows a password change. If the change fails or is not required, an exception is thrown. The exception message is translated at the client and displayed to the user if necessary. | ''changePassword'' allows a password change. If the change fails or is not required, an exception is thrown. The exception message is translated at the client and displayed to the user if necessary. | ||
| - | ''logout'' tells the security manager that the session was ended. This is either done manually by the user, or automatically after the expiration of the timeout period. | + | ''logout'' tells the security manager that the session was ended. This is either done manually by the user or automatically after the expiration of the timeout period. |
| - | ''getAccessController'' limits access to [[jvx:server:lco:lifecycle|Lifecycle Objects]]. This method is called when a MasterConnection is established to control access to SubConnections and SubSessions. When a SubConnection is established, we can verify if access is allowed using IAccessController.isAllowed. | + | ''getAccessController'' limits access to [[jvx:server:lco:lifecycle|Life Cycle Objects]]. This method is called when a master connection is established to control access to sub-connections and sub-sessions. When a sub-connection is established, we can verify if access is allowed using IAccessController.isAllowed. |
| ''release'' tells the security manager that all used resources should be released. | ''release'' tells the security manager that all used resources should be released. | ||
| - | == Using the security manager == | + | == Using the Security Manager == |
| The security manager has to be defined in the configuration file of the application (config.xml), to ensure that it is used at the next login attempt. For example: | The security manager has to be defined in the configuration file of the application (config.xml), to ensure that it is used at the next login attempt. For example: | ||
| Line 194: | Line 194: | ||
| **<fs 20px>Note</fs>** | **<fs 20px>Note</fs>** | ||
| - | The standard configuration only instantiates a security manager once per application and it is reused at every login attempt. It is therefore important to pay attention to synchronization and to make sure that the constructor does not contain essential code. | + | The standard configuration only instantiates a security manager once per application, and it is reused at every login attempt. It is, therefore, important to pay attention to synchronization and to make sure that the constructor does not contain essential code. |
| - | It's also possible to create a security manager per Session, but this needs manual configuration. | + | It's also possible to create a security manager per session, but this needs manual configuration. |