[wildfly-dev] Servlet Samples on Beta2 snapshot

[Arun Gupta]

If I invoke this command on a local instance of WildFly then it works.
Giving this command on a CI test build gives the error:

Exception in thread "main" java.lang.IllegalStateException:
JBAS015232: No java.io.Console available to interact with user.
at org.jboss.as.domain.management.security.adduser.AddUser.<init>(AddUser.java:104)
at org.jboss.as.domain.management.security.adduser.AddUser.<init>(AddUser.java:131)
at org.jboss.as.domain.management.security.adduser.AddUser.main(AddUser.java:230)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.modules.Module.run(Module.java:292)
at org.jboss.modules.Main.main(Main.java:455)

What would be the equivalent jboss-cli command for it ?

In general, how do guide our users to convert these command to jboss-cli ?

Arun

On Fri, Nov 1, 2013 at 12:50 PM, Darran Lofthouse
<darran.lofthouse at jboss.com> wrote:
> To add an application user to the default properties file (with groups) the
> following command should be all that is required: -
>
> ./add-user.sh -a -u u1 -p p1! -g a,b,c
>
> Regards,
> Darran Lofthouse.
>
>
> On 01/11/13 19:42, Darran Lofthouse wrote:
>>
>> On 01/11/13 19:37, Arun Gupta wrote:
>>>
>>> Stuart,
>>>
>>> I was not saying this is a bug, just trying to understand better. Each
>>> realm can use different property file but does that information needs
>>> to be exposed to the user ?
>>
>>
>>
>> It should not need to be, the -ug and -gp arguments were added for users
>> using non standard property file names so with a default installation
>> these should not be required.
>>
>> Instead the '-a' argument should be used to specify the an application
>> user is being added instead of the default mode which is to add a
>> management user.
>>
>> Also specifying the realm name should not be required, all users in a
>> single properties file must share the same realm so that is now
>> automatically discovered from the default files.
>>
>>>
>>> Nick,
>>>
>>> Default behavior is good but a non-interactive mode is more likely to
>>> be used IMHO.
>>>
>>> Arun
>>>
>>> On Fri, Nov 1, 2013 at 12:16 PM, Nikolaos Ballas <mpallas at gmail.com>
>>> wrote:
>>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA256
>>>>
>>>> On that I agree with Stuart,
>>>>
>>>> you can use the script without arguments and it will guide you through
>>>> also by checking other stuff and informs you about the security you
>>>> want to apply. It will put you to select the realm and do the
>>>> configuration accordingly.
>>>>
>>>> regards
>>>> Nick
>>>> On 01/11/2013 19:08, Stuart Douglas wrote:
>>>>>>
>>>>>>
>>>>>> Thanks for the complete command, that worked!
>>>>>>
>>>>>> Just wondering what other values can be taken by the last two
>>>>>> arguments ? And why would they need a different value ?
>>>>>>
>>>>>
>>>>> because each realm uses a different property file. TBH I am not
>>>>> sure if this is a bug or not. if you use the tool without any
>>>>> arguments it automatically does the right thing. Perhaps someone
>>>>> who is more familiar with the tool could comment.
>>>>>
>>>>> Stuart
>>>>>
>>>>>
>>>>>>
>>>>>> Arun
>>>>>>
>>>>>> http://blog.arungupta.me http://twitter.com/arungupta
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________ wildfly-dev mailing
>>>>> list wildfly-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>
>>>>
>>>> -----BEGIN PGP SIGNATURE-----
>>>> Version: GnuPG v1.4.12 (GNU/Linux)
>>>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>>>
>>>> iF4EAREIAAYFAlJz/hMACgkQM4d5SPwi8EusKwEAg+/nDApRkExcQ3Bqh4u7L4zA
>>>> t/40dNNQIN+GdPpkS4AA/1pgrbBRo6R2f46qMlv/y/6ljQiVbhiYNEjguoEwbzg5
>>>> =n46e
>>>> -----END PGP SIGNATURE-----
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> wildfly-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>>
>>>
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>



-- 
http://blog.arungupta.me
http://twitter.com/arungupta