isurangaperera / cli Goto Github PK

This is something we can do as we go along. Not a top priority.

Handle things like,

• Configs not set properly
• Endpoint not available etc.

Currently in the config command we set the following,

1. Username and Password to do the service calls
2. Base URL
3. Service Endpoints

IMO, we can get rid of configuring service endpoints since we already know them and they are not going to change. For example: UserAdmin endpoint will always be services/UserAdmin.UserAdminHttpsSoap11Endpoint or services/UserAdmin.UserAdminHttpsSoap12Endpoint/ and only the baseURL might change.

Even the baseURL we can have a default value of localhost:9443 and override the value if someone sets it using the config command.

Also noticed that config command gives an error although it was successful...

Shall we update the README.md with the expected outputs of each cli command?

ListAllUsers operation works fine. But I noticed that it prints out an additional empty user when listing.
Checkout the screenshot below. I have two created two users in my Identity Server but the commands prints out three uses, last one being an empty one.

Will you be able to add a README file with instructions to setup and run this CLI tool?
This will help anyone to try out this tool easily.

I went ahead and excuted ./cli listAllUsers
Here's the output I got. Can you explain the output?

Tried running the tool following the instructions given in the README.md

  farazath  ~/Desktop/cli   master   cli config -url localhost:9443 -u admin -p password 
The assembly mscorlib.dll was not found or could not be loaded.
It should have been installed in the `/usr/lib/mono/2.0/mscorlib.dll' directory.

looks like additional libs are required... would be great if you could have some info to build from source.

As I understood the cli config command initializes the credentials necessary to do the service calls to SOAP endpoints?

I tried executed the command and got the below output

Can you explain what is the expected output?

At the moment addInternalRole does two things if I understood correctly,

1. Create an internal role with specified permissions.
2. Assign the internal role to specified user.

addInternalRole gives the idea we are simply creating an internal role with a set of permissions. Maybe we could improve the name to include the idea that users are assigned to the created role as well..

the use of -p to represent permissions is confusing since we already use that for representing password in the config command. May be we should use -permissions to represent this....

Upon successful creation, the tool does not give any feedback. Maybe printing something like
"Internal Role X assigned to User Y" would be great...