Dear Jonathan,
As a client of AAI, we are told that multicloud micro-services
follow the rule “Each system should be issued its own ID in AAF ” . So I would
like to have your help to understand following questions:
1, What the ID looks like? Is it a static UUID or dynamic one generated during
run-time ?
2, Giving the context that MultiCloud has not integrated with AAF, but AAI
does, Is that possible that MultiCloud to use this ID to interact with AAI ?
3, How we can apply the ID?
Thanks
Best Regards,
Bin Yang, Solution Engineering Team, Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189
Skype: yangbincs993
From: [email protected] [mailto:[email protected]] On
Behalf Of Yang Bin
Sent: Tuesday, September 18, 2018 11:01 AM
To: [email protected]; [email protected]
Cc: HUANG, HAIBIN ([email protected]); Ethan Lynn ([email protected]);
Morales, Victor; Sudhakar Reddy ([email protected]); HU, BIN
([email protected]); [email protected]; Xinhui Li ([email protected]);
Zhang, Xiaohua
Subject: Re: [onap-discuss] New authentication and authorization in Casablanca
for #aai
Dear Jimmy,
Mulit-VIM/Cloud is client of AAI as well.
I hope this transition will not impact M4 so that we can figure
out how to comply with this new rule. Thanks
Best Regards,
Bin Yang, Solution Engineering Team, Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189
Skype: yangbincs993
From: [email protected] [mailto:[email protected]] On
Behalf Of Jimmy Forsyth
Sent: Tuesday, September 18, 2018 10:44 AM
To: [email protected]
Subject: [onap-discuss] New authentication and authorization in Casablanca for
#aai
Dear AAI Clients,
AAI is still using HTTPS basic authentication in Casablanca but since we are
integrating with AAF we cannot continue to use the existing usernames and
passwords since all the ones we created in the demo in Amsterdam are against
AAF standards – therefore, I cannot port into AAF the existing credentials that
have been used to talk to AAI.
I have reached out directly to the PTLs of the major clients of AAI about this
upcoming change in usernames and passwords, so they should be covered (robot,
so, sdnc, dcae, policy, sdc, vid, appc, and oof).
I have two open commits for both HEAT and OOM environments so that your teams
will be able to transition to the new usernames/passwords before we move to
AAF, which will allow us to turn on the AAF enforcement without a flash cut and
hopefully without any interruptions for those clients who have taken the step
of converting to the new credentials.
For the rest of you who may be piggy-backing off these legacy credentials and
your project is not listed above, the credential you have been using *will stop
working* once AAI has enabled Authentication and Authorization with AAF. Let
me say that again: the usernames and passwords that you have been using will
stop working once we enable AAF in AAI – we were hoping to get there by M4 but
we are unlikely to reach that goal so it will be implemented shortly after M4.
Each system should be issued its own ID in AAF; if your system has not been set
up in AAF I recommend reaching out to the AAF team ASAP (Jonathan Gathman is
the PTL) and then let me know what your application id is.
Please let me know soon so we can make this transition as painless and seamless
as possible.
Thanks,
Jimmy Forsyth
AAI PTL
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12491): https://lists.onap.org/g/onap-discuss/message/12491
Mute This Topic: https://lists.onap.org/mt/25742174/21656
Mute #aai: https://lists.onap.org/mk?hashtag=aai&subid=2740164
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
