Versions Compared

Old Version 22

changes.mady.by.user Jamey McCabe

Saved on

compared with

New Version 23

changes.mady.by.user Jamey McCabe

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimingItemWhoNotes
10 minGreet and begin sharing and communicating in all channels (here, conference bridge, IRC)

20 minAttendees (hopefully at least 1 from each member company) introduce themselves and their interest/challenges

NTT: We had two major requirements in regards to RBAC

  1. Restrict users to access in-mature APIs (API parameters). We wanted to allow only well-tested APIs since maturity of API was not the same even within one project.
    1. we used reverse proxy (mod-proxy, etc) to filter API request (for public endpoint)
  2. Hierarchical Admin roles (mid-level admins and high-level admins whose area of management is different. i.e. high-level can access to all tenant resources but mid-level can only access to limited tenants)
    1. we tried to use "domains" and os-inherit feature to do some part of this but the configuration became too complicated and did not scale.
30 minDiscussion topic/presentation #1Orange

Presentation of External Policy Decision Point and Moon.

LCOO_Orange_IAM_Clouds-v2.pptx

to view: https://coopnet.multimedia-conference.orange-business.com/Login/ParticipantLogin.aspx?id=12413772&key=%3f%3fq%3fx%3fFQ%3fF%3f%5e%3fS%3f%3f&a=participate

30 min


Discussion topic/presentation #2AT&T

Role Based Access Control Challenges & Solutions

Role-Based Access Control Challenges Solutions Draft v4.pdf

30 minOpen Discussion/Next Steps

We can put proposed next steps here.  This could include subsequent sessions or checkpoints in which we bring others in.


Action items

    •