Not clear Documentation or Commands

[pavrip]

Hi
I am just getting started with Jakarta EE & Wildfly.

The documentation with Jakarta EE is hard enough, Wildly looks good but its not properly clear.

It is taking me over 3 hours just to add a new user.

I have followed the commands, gone to ./add-user.sh put user name and password,

Now it's asking me to do this:

To represent the user add the following to the server-identities definition

Now, where on earth am I supposed to put this? No information on google, no information on what file?

Is there a tag somewhere? I checked on one article, but no information about the file.

Any advice would be appreciated

[jamezp]

What version of WildFly are you using?

[pavrip]

Hi It’s the latest version 23.0

…

On Tue, 16 Mar 2021 at 00:33, James R. Perkins ***@***.***> wrote: What version of WildFly are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK35EKUDJLD4U7EN3LXDANLTD2RONANCNFSM4ZHJPHNA> .

[jamezp]

https://docs.wildfly.org/23/Admin_Guide.html#domain-controller-configuration talks about this being used for domain mode. What is your end goal?

[pavrip]

My end goal was to learn how to administer/manage the server and learn about it from the ground up.
If there is a place where I can get all the documentation organised in one place, I would start.

[jamezp]

Really that is the spot for documentation. We're working on improving it for sure. This could be useful as well https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html/configuration_guide/index

[bstansberry]

Apologies if this is already understood, but the code in this repo is published in html form at https://docs.wildfly.org. There's a subdirectory for each release, so the landing page for the latest release is https://github.com/wildfly/wildfly.github.io/23/ which describes the various documents. https://docs.wildfly.org/23/Getting_Started_Guide.html is a possible starting point

If the add-user.sh script has output the 'To represent the user add the following to the server-identities definition ' line this means you previously answered 'yes' to this question:

Is this new user going to be used for one AS process to connect to another AS process? 
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server Jakarta Enterprise Beans calls.
yes/no?

Unless you are currently setting up a multi-host WildFly managed domain and the user you are creating is how one host is going to identify itself to the Domain Controller, the answer to that should be 'no'. If it really should be 'yes' the 'secret-identities' configuration it refers to is documented at https://docs.wildfly.org/23/Admin_Guide.html#server-identities.

I filed https://issues.redhat.com/browse/WFLY-14645 to get the Getting Started Guide updated to note the answer to this question should be 'no' for the kind of user it is describing adding.

[pavrip]

Thank you for this. I have managed to look into that, I apologise for the delay.
I have found setting up the environment very complicated and difficult.
I have downloaded this with Brew on my Mac again.

I cannot explain what a confusing developer experience I have had, I have spent more time trying to just do basic things instead of getting on with building software

On the access control page, I see a massive error :

I cant even add a Data Source as the page is blank and no options:

The problem with these kinds of dead-end errors, is that I dont know if I have done something wrong or if there is a bug in the server.
I don't even know what kind of question to ask or where to look for help.

[bstansberry]

I'm sorry you're having difficulty.

The best way to try to get help from the WildFly community is to post questions on the WildFly forum at https://groups.google.com/g/wildfly. It's community software so there's no guarantees you'll get what you need, but the forum is the best place to ask.