Here are additional details :
To create a user to not use the one created by default, he need to play this
command on the server where is send the request:
{JBOSS_HOME}/bin/add-user.sh (JAVA_HOME should be well set to java 1.8)
And then reply to the questions like this:
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): b
Enter the details of the new user to add.
Using realm 'ApplicationRealm' as discovered from the existing property files.
Username : username_you_want
Password recommendations are listed below. To modify these restrictions edit
the add-user.properties configuration file.
- The password should be different from the username
- The password should not be one of the following restricted values {root,
admin, administrator}
- The password should contain at least 8 characters, 1 alphabetic character(s),
1 digit(s), 1 non-alphanumeric symbol(s)
Password : valid_password
Repeat the password
What groups do you want this user to belong to? (Please enter a comma separated
list, or leave blank for none)[ ]: InfraPortal-Client (or another valid group
or list of valid groups depending of what the user need to do)
About to add user 'user1' for realm 'ApplicationRealm'
Is this correct yes/no? yes
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 EJB calls.
yes/no? no
The result is stored in
{JAVA_HOME}/domain/configuration/application-roles.properties and
{JAVA_HOME}/domain/configuration/application-users.properties
To make it permanent at each build, you can also change these 2 files by adding
the 2 entries generated above in onap mso repository under
packages/docker/src/main/docker/docker-files/jboss-configs/configuration/
Thanks,
Eddy & Seb
From: [email protected]
[mailto:[email protected]] On Behalf Of Determe, Sebastien
Sent: Friday, June 16, 2017 9:51 AM
To: Kedar Ambekar <[email protected]>; [email protected]
Subject: Re: [onap-discuss] User that VID uses to call MSO APIs ?
***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hi,
To add a new user associated to the VID interface, you must use the JBOSS
script located in the MSO container "/opt/jboss/bin/add-user.sh".
The script is going to ask you for a few parameters such as the
Group/Username/password/is for EJB calls or not.
You must set the group to "InfraPortal-Client" for the VID interfaces and you
must answer "NO" to EJB calls.
Thanks,
Seb
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kedar Ambekar
Sent: Friday, June 16, 2017 1:47 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] User that VID uses to call MSO APIs ?
Thank you Daniel, that worked.
Also, do you know how to create a user on MSO side for these APIs ?
From: ROSE, DANIEL V [mailto:[email protected]]
Sent: Friday, June 16, 2017 12:35 AM
To: Kedar Ambekar <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: RE: User that VID uses to call MSO APIs ?
Try InfraPortalClient/password1$
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kedar Ambekar
Sent: Thursday, June 15, 2017 9:54 AM
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] User that VID uses to call MSO APIs ?
Hi,
May I know what username / password VID application uses while invoking MSO
APIs like Create Service Instance / Create VNF etc ?
By referring to VID's system.properties and some code, I tried with infraportal
/ infra-R1510! , but that doesn't seem to be working.
Also if I want to create a user in MSO for these APIs, how to do that ?
Thanks !
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary
and confidential and subject to the Tech Mahindra policy statement, you may
review the policy at
http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=haXpG2fMpqHNQk5e_JkN10Emmp55r7jC8DK7vVdlrCU&s=MleTgkzmkpSn7zbBql44vvvYFzAGKk3cTu_7hAsukjM&e=>
externally
http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=haXpG2fMpqHNQk5e_JkN10Emmp55r7jC8DK7vVdlrCU&s=-gjzI_KDzA_NMkEuuKX7V1rttm-eOTKPqp4BpChLKo0&e=>
internally within TechMahindra.
============================================================================================================================
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
