master
stable/zed
stable/yoga
stable/ussuri
stable/xena
stable/wallaby
stable/victoria
stable/train
stable/stein
stable/rocky
feature/falcon-api-framework
queens-eol
wallaby-em
8.0.0
8.0.0.0rc2
8.0.0.0rc1
pike-eol
victoria-em
7.0.0
7.0.0.0rc2
7.0.0.0rc1
4.1.0
ussuri-em
6.0.0
6.0.0.0rc2
6.0.0.0rc1
3.0.1
ocata-eol
train-em
5.0.0
5.0.0.0rc3
5.0.0.0rc2
5.0.0.0rc1
2.0.2
stein-em
4.0.0
4.0.0.0rc3
4.0.0.0rc2
4.0.0.0rc1
1.0.1
2.0.1
3.0.0
3.0.0.0rc2
3.0.0.0rc1
rocky-em
queens-em
2.0.0
2.0.0.0rc1
pike-em
0.8.2
ocata-em
1.0.0
1.0.0.0rc2
1.0.0.0rc1
0.10.0
0.9.0
0.8.1
newton-eol
0.8.0
mitaka-eol
0.7.0
0.6.0
liberty-eol
0.5.0
0.4.0
kilo-eol
0.3.1
0.3.0
0.2.1
0.2.0
0.1.0
${ noResults }
1 Commits (ab50e471b976d2820b8f2ff30de1534491e79f3a)
Author | SHA1 | Message | Date |
---|---|---|---|
![]() |
ab50e471b9 |
Auth parameters for uploading vnf package from URI
Upload VNF Package from uri REST API accepts userName and password parameter but internally these parameters are not used while getting the csar zip file from the URI as specified in the addressInformation. If the server serving the CSAR zip requires authentication, it would return 401 error and the uploading vnf package will fail to set the VNF package to onboarded status. This patch uses userName and password parameters to set "Authorization" header as shown below if these parameters are passed in the request body. * The userName and password are combined with a single colon (:). This means that the username itself cannot contain a colon. * The resulting string is encoded using a variant of Base64. * The authorization method (Basic and a space (e.g. "Basic ") is then prepended to the encoded string. For example, if userName and password is "xyz" and "xyzpassword", then the field's value is the base64-encoding of xyz:xyzpassword, or eHl6Onh5enBhc3N3b3Jk. Then the Authorization header will appear as: Authorization: Basic eHl6Onh5enBhc3N3b3Jk Change-Id: Ie79d5e4659951f41db4a1003950c649acab8b439 |
3 years ago |