THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Wiki Markup |
---|
{div:class=confluenceTableSmall} || Name || Default Value || Type || Description || | {{iniResourcePath or ini}} | {{none}} | Resource String or Ini Object | A mandatory Resource String for the iniResourcePath or an instance of an Ini object must be passed to the security policy. Resources can be acquired from the file system, classpath, or URLs when prefixed with "file:, classpath:, or url:" respectively. For e.g "classpath:shiro.ini" | | {{passPhrase}} | {{An AES 128 based key}} | byte[] | A passPhrase to decrypt ShiroSecurityToken(s) sent along with Message Exchanges | | {{alwaysReauthenticate}} | {{true}} | boolean | Setting to ensure re-authentication on every individual request. If set to false, the user is authenticated and locked such than only requests from the same user going forward are authenticated. | | {{permissionsList}} | {{none}} | List<Permission> | A List of permissions required in order for an authenticated user to be authorized to perform further action i.e continue further on the route. If no Permissions list or Roles List (see below) is provided to the ShiroSecurityPolicy object, then authorization is deemed as not required. Note that the default is that authorization is granted if any of the Permission Objects in the list are applicable. | | {{cipherServicerolesList}} | {{AESnone}} | org.apache.shiro.crypto.CipherServiceList<String> | Shiro ships with AES & Blowfish based CipherServices. You may use one these or pass in your own Cipher implementation*Camel 2.13:* A List of roles required in order for an authenticated user to be authorized to perform further action i.e continue further on the route. If no roles list or permissions list (see above) is provided to the ShiroSecurityPolicy object, then authorization is deemed as not required. Note that the default is that authorization is granted if any of the roles in the list are applicable. | | {{cipherService}} | {{AES}} | org.apache.shiro.crypto.CipherService | Shiro ships with AES & Blowfish based CipherServices. You may use one these or pass in your own Cipher implementation | | {{base64}} | {{false}} | {{boolean}} | *Camel 2.12:* To use base64 encoding for the security token header, which allows transferring the header over [JMS] etc. This option must also be set on {{ShiroSecurityTokenInjector}} as well. | | {{base64allPermissionsRequired}} | {{false}} | {{boolean}} | *Camel 2.1213:* To use base64 encoding for The default is that authorization is granted if any of the securityPermission tokenObjects header,in whichthe allowspermissionsList transferringparameter theare headerapplicable. overSet [JMS] etc. This option must also be set on {{ShiroSecurityTokenInjector}} as wellthis to true to require all of the Permissions to be met. | | {{allPermissionsRequiredallRolesRequired}} | {{false}} | {{boolean}} | *Camel 2.13:* The default is that authorization is granted if any of the Permission Objectsroles in the permissionsListrolesList parameter are applicable. Set this to true to require all of the Permissionsroles to be met. | {div} |
Applying Shiro Authentication on a Camel Route
...