That file has the updated password K*U. I would destroy the docker container and re-pull it.
Brian From: MAJHI, TAPAN Sent: Saturday, June 03, 2017 6:35 AM To: FREEMAN, BRIAN D <bf1...@att.com>; Ahmad, Munir <munir.ah...@bell.ca>; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] SDNC throwing error Unauthorized for all rest calls No luck ☹ I took the latest file copied to the location you asked and tried. Still not able to login to the webportal of SDNC. And getting the same 401 Unauthorized error on rest calls. Password should change or remains the same after this process ? Regards, Tapan M From: FREEMAN, BRIAN D [mailto:bf1...@att.com] Sent: Friday, June 02, 2017 6:32 PM To: Tapan Majhi <tapan.ma...@amdocs.com<mailto:tapan.ma...@amdocs.com>>; Ahmad, Munir <munir.ah...@bell.ca<mailto:munir.ah...@bell.ca>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] SDNC throwing error Unauthorized for all rest calls Not sure it will fix your problem but try recopying the idmlight.db.mv.db file from gerrit into /opt/opendaylight/current inside the container. The file with the password is replaced during the container creation so this “should” reset it. sdnc/oam/installation/sdnc/target/docker-stage/Dockerfile:COPY idmlight.db.mv.db /opt/opendaylight/current Brian From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of MAJHI, TAPAN Sent: Friday, June 02, 2017 8:42 AM To: Ahmad, Munir <munir.ah...@bell.ca<mailto:munir.ah...@bell.ca>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] SDNC throwing error Unauthorized for all rest calls Tried restarting the container , issue remains the same. For the webportal I am unable to login since it requires credential and the current credential is not working. "admin" - "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" Any idea where can we reset this password or which bundle in SDNC is responsible for the authentication functionality ? Regards Tapan m From: Ahmad, Munir [mailto:munir.ah...@bell.ca] Sent: Friday, June 02, 2017 5:59 PM To: Tapan Majhi <tapan.ma...@amdocs.com<mailto:tapan.ma...@amdocs.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] SDNC throwing error Unauthorized for all rest calls Hi Tapan, Did you try restarting the sdnc_controller_container? I would try to recreating the container if restart doesn’t fix it. You also can preload your VNF through API docs web portal here is the link to preload VNF topology. http://localhost:8282/apidoc/explorer/index.html#!/VNF-API(2015-07-20)/preload_vnf_topology_operation_post_475<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8282_apidoc_explorer_index.html-23-21_VNF-2DAPI-282015-2D07-2D20-29_preload-5Fvnf-5Ftopology-5Foperation-5Fpost-5F475&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=QXNm0wXsZY9qnVes7N3FeqblMNJf6oqTZGycYF009BA&s=FGJ_Njzbjc-VegWb27eryD92qyiWg79IiiEGS4aXb4c&e=> Thanks Munir From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Tapan Majhi <tapan.ma...@amdocs.com<mailto:tapan.ma...@amdocs.com>> Date: Friday, June 2, 2017 at 4:57 AM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: [onap-discuss] SDNC throwing error Unauthorized for all rest calls My working SDNC container suddenly started giving error for all the rest calls . root@4712c8e7d331:/# curl -k -X POST -i -H "Content-Type: application/json" -H "Accept: application/json" -H "Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==" -H "X-TransactionId: 0a3f6713-ba96-4971-a6f8-c2da85a3176e" -H "X-FromAppId: API client" -H "Expect:" http://localhost:8181/restconf/operations/VNF-API:preload-vnf-topology-operation<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8181_restconf_operations_VNF-2DAPI-3Apreload-2Dvnf-2Dtopology-2Doperation&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=QXNm0wXsZY9qnVes7N3FeqblMNJf6oqTZGycYF009BA&s=-dRl6sxzGaKn5CfpmhwsLuNV8g31B6tfvjk1TD_FlP8&e=> --data-binary @./req.json HTTP/1.1 401 Unauthorized Set-Cookie: rememberMe=deleteMe; Path=/restconf; Max-Age=0; Expires=Sun, 01-Jun-2017 21:06:16 GMT WWW-Authenticate: BASIC realm="application" Content-Length: 0 Server: Jetty(8.1.15.v20140411) Now I am not even able to login to the swagger with below credentials. "admin" - "Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U" Which was working fine day before. I have checked all the bundles two bundles are in resolved state.Rest all are in active state. 14 | Resolved | 20 | 1.0.0 | Apache Aries Blueprint Core Compatiblity Fragment Bundle, Hosts: 15 117 | Resolved | 80 | 0.4.2.Beryllium-SR2 | org.opendaylight.controller.config-persister-file-xml-adapter, Hosts: 118 Any idea what went wrong and how to fix it ? Regards, Tapan M This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=QXNm0wXsZY9qnVes7N3FeqblMNJf6oqTZGycYF009BA&s=58rDW9NcNRJJ7aeZ_Rir952qYDIbzjpyduQ0XoNDkdw&e=> Amdocs Development Centre India Private Limited having CIN: U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A limited liability partnership with LLP Identification Number: AAI-6901 effective 28th Feb 2017) This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=QXNm0wXsZY9qnVes7N3FeqblMNJf6oqTZGycYF009BA&s=58rDW9NcNRJJ7aeZ_Rir952qYDIbzjpyduQ0XoNDkdw&e=> Amdocs Development Centre India Private Limited having CIN: U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A limited liability partnership with LLP Identification Number: AAI-6901 effective 28th Feb 2017) This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=TIgafjCM7V123OWyhGzLysOdsLtA5qaSH07n9qlRL38&s=QdaWMxHR5mJLTgegX7AC1rQ06BjQiFlYIgQVOWbdZNY&e=> Amdocs Development Centre India Private Limited having CIN: U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A limited liability partnership with LLP Identification Number: AAI-6901 effective 28th Feb 2017)
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
