Should add that a pull request has now gone into master where the local
mechanism is now specified within the realm - removing the <local />
element from the realm will also disable the mechanism.
Regards,
Darran Lofthouse.
On 04/19/2012 04:03 AM, Jason T. Greene wrote:
You can also switch users or use an IP address that isn't a
loopback
address.
On 3/27/12 4:47 AM, Darran Lofthouse wrote:
> Hello,
>
> The folder you are looking for is standalone/tmp/auth - locally when I
> am testing I just change the ownership to root - an alternative could be
> to change it from a folder to a file so a new folder with the same name
> can not be created.
>
> If this is still an issue for you let me know and we can review
> alternatives.
>
> Regards,
> Darran Lofthouse.
>
>
> On 03/27/2012 09:38 AM, Jan Lanik wrote:
>> Hi,
>>
>> do you know how the mechanism which disables security check for CLI
>> access from the same machine works?
>> I've been told that some ticket is generated by server and this
>> ticket is then used by cli client for authentication.
>> I need to know where exactly is this ticket located and how to block
>> the client from accessing it (delete ticket, restrict access..)
>> so that it is forced to use standard authentication as if it was run
>> from a different machine.
>>
>> The goal is to test the authentication for CLI - running it on two
>> machines would be too complicated, so we need somehow bypass
>> that mechanism.
>>
>> Thanks for any advice,
>>
>> Jan
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev