Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
jvx:server:security:manager [2018/02/02 08:15] admin |
jvx:server:security:manager [2018/02/02 08:20] admin |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| == 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: |
| <file java HashtableSecurityManager.java> | <file java HashtableSecurityManager.java> | ||
| Line 150: | Line 150: | ||
| </file> | </file> | ||
| - | The interface com.sibvisions.rad.server.security.ISecurityManager defines the methods | + | The interface ''com.sibvisions.rad.server.security.ISecurityManager'' defines the methods |
| <file java> | <file java> | ||
| Line 196: | Line 196: | ||
| 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 use a security manager per Session, but this isn't the standard configuration. | + | It's also possible to create a security manager per Session, but this needs manual configuration. |