[
https://issues.apache.org/jira/browse/SHIRO-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Les Hazlewood resolved SHIRO-125.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.0
This was implemented by making the implicitly created IniRealm available in the
[main] section. The existence of a non-empty [users] or [roles] sections will
trigger the 'iniRealm' object to be available for configuration like any other
object in the [main] section.
[main]
...
credentialsMatcher = org.apache.shiro.authc.credential.Sha256CredentialsMatcher
iniRealm.credentialsMatcher = $credentialsMatcher
...
[users]
admin = 2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b,
role1, role2, ...
...
The
IniSecurityManagerFactoryTest.testImplicitIniRealmWithAdditionalRealmConfiguration
test case shows validation.
> Support overrding the credentialsMatcher for the implicit IniRealm
> ------------------------------------------------------------------
>
> Key: SHIRO-125
> URL: https://issues.apache.org/jira/browse/SHIRO-125
> Project: Shiro
> Issue Type: Improvement
> Components: Configuration, Realms
> Reporter: Philippe Laflamme
> Fix For: 1.0
>
>
> When using the implicit IniRealm, it would be useful to override the
> credentialsMatcher to support, non-plaintext passwords in the [users] section.
> Example shiro.ini:
> ---
> [main]
> # The [users] section will contain SHA256 hashed passwords
> credentialsMatcher=org.apache.shiro.authc.credential.Sha256CredentialsMatcher
> [users]
> # Hex value of SHA256 hashed password
> aUser=28eeeb5e16f38c67dfcc73733ee3649f9b0adcc2a6cfc957d40814348459ee7c
> ---
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
