-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
Original:
ONAP MUST have the capability of allowing the Operator to create, manage, and automatically provision user accounts using an Operator approved identity lifecycle management tool using a standard protocol.
Notes: Compared to VNF reqs, I removed from the end "eg. NETCONF API" because I do not think it is good choice for ONAP. But we should specifiy which standard protocol.
Requirement is removed. Motivation:
- Authentication is not in the scope of ONAP, but shall be externalized.
- Exception: the ONAP super-user default account. For this, no password expiration should be defined.