Apache Wicket 8.x Reference Guide22.1. Authentication The first step in implementing a security policy is assigning a trusted identity to our users, which means that we must authenticate them. Web applications usually adopt a form-based every subclass of AuthenticatedWebSession. It should contain the actual code that checks for user’s identity. It returns a boolean value which is true if authentication has succeeded or false otherwise.0 码力 | 350 页 | 9.95 MB | 1 年前3- Apache Wicket 7.x Reference Guide22.1. Authentication The first step in implementing a security policy is assigning a trusted identity to our users, which means that we must authenticate them. Web applications usually adopt a form-based every subclass of AuthenticatedWebSession. It should contain the actual code that checks for user’s identity. It returns a boolean value which is true if authentication has succeeded or false otherwise.0 码力 | 346 页 | 10.00 MB | 1 年前3
- Apache Wicket 10.x Reference Guide22.1. Authentication The first step in implementing a security policy is assigning a trusted identity to our users, which means that we must authenticate them. Web applications usually adopt a form-based every subclass of AuthenticatedWebSession. It should contain the actual code that checks for user’s identity. It returns a boolean value which is true if authentication has succeeded or false otherwise.0 码力 | 336 页 | 7.16 MB | 1 年前3
- Apache Wicket 9.x Reference Guide22.1. Authentication The first step in implementing a security policy is assigning a trusted identity to our users, which means that we must authenticate them. Web applications usually adopt a form-based every subclass of AuthenticatedWebSession. It should contain the actual code that checks for user’s identity. It returns a boolean value which is true if authentication has succeeded or false otherwise.0 码力 | 335 页 | 7.15 MB | 1 年前3
共 4 条
- 1