On 31/03/15 16:52, arjan tijms wrote:
> Hi,
>
> On Tue, Mar 31, 2015 at 5:25 PM, Darran Lofthouse
> <darran.lofthouse_at_redhat.com> wrote:
>> @DataSourceDefinition(
>> name="java:app/jdbc/test",
>> className="com.mysql.jdbc.jdbc2.optional.MysqlDataSource",
>> user="root",
>> password="${ALIAS=password}",
>> databaseName="test",
>> serverName="localhost",
>> portNumber=3306 )
>
> When I see password="${ALIAS=password}", I think it strongly resembles
> one of the proposals in the Configuration JSR; EL based placeholders
> in XML and annotations. I haven't really looked at the password
> aliasing proposal in detail lately, but what's stopping this from
> being used for all other attributes as well?
Maybe this is a problem to be split into two pieces: -
1. General aliasing which would enable secure storage of the alias
values, that covers today and the existing passwords in config.
2. A more complete "identity aliasing" which covers obtaining an
identity in general for outbound connections.
> E.g.
>
> serverName="${ALIAS=serverName}
>
> ?
>
> Kind regards,
> Arjan Tijms