Scribing Template --Friday, Oct 5, 2012 at 10am Salon 3
TOPIC: How PersonRegistry Fits your Idms document
CONVENER: Omer Almatary, Dave Steiner (Rutgers University)
SCRIBE: Muhammad Siddique
# of ATTENDEES:
MAIN ISSUES DISCUSSED
- Rutgers PersonRegistry based on Jasig OpenRegistry
- Objective: Help to build the Road Map items
- Existing core component (OpenRegistry 0.9.1 v) :
- UI
- Guest Management
- Early Faculty/Staff On boarding
- Generate Activation keys
- View Person
- Overwrite SoR data
- Split/Join a person
- Add Person
- Batch
- From SoR
- Load
- Validate
- Normalize
- Standardize
- Reconcile (Identity Match)
- Calculate
- Elect
- Identifiers assignment
- non-person entities
- REST API (Upstream)
- Support for Audit
- Support for Provisioning/De provisioning (Routing engine)
- Authorization Module
- Support Disclosure setting
- Views (Data out:Rutgers Specific)
- UI
- What is missing : ?
- Comment:Password manage in OR?
- Observation:No password management in OR. But OR has password meta data (activation key) available via REST api.
- Comment: is self service part of OR? Or extension or separate product
- Comment: What about disclosure?
- Observation:Disclosure data is in OR but its UI (disclosure settings UI) is different production .
- It should be separate product. May be separate product can be used by the community that talk to the OR.
- There should be some kind of boundary defined for self services.
- Comment: RESt api for workflow should be documented
- Comment:Personal public profile in person registry?
- Observation: UI /Rest Api can be used as self service.
- Observation:Some kind of self service is available in SOR. (People soft self service)
- Comment: Some SPI want to get personal public profile (google ) they should come to IDM vs getting it from SOR.
- Comment:User don't understand different system, Next gen system should display aggregate date from different sors
- Comment:Some kind of self service should be available in Registry
- Question:What kind of data, OR is authorative data source
- Observation: Registry just generate guest data, OR some kind of identifiers
- Comment:What kind customization OR provide
- Observation: Rutgers have extensible (overlayed UI). There is effort going on to make it generic and make it available to the community,. We also have extensible data model for identifiers. But It is more of programming vs configuration or the dynamic configuration via UI.
- Question: is there any administrative UI to monitor the performance etc?
- Observation: There is admin UI , but it doesn't support monitoring.
- Comment: What does it take to replace SUN idm with OR?
- Comment: Is provisioning is part OR or the separate team?
- Observation: In I2 there is different team for provisioning
- Comment: Is class schedule is part of registry?
- Observation: Historical people do that but it should not be the part of IDM
- Comment: Do you think OR as IDM or the data services?
- Observation: Most people do that , ideally it should be just IDM (just like sun IDM , a head without body). Data master services should be separate (reporting services).
- Comment: Push vs Pull for provisioning
- Observ: Most commercial products do that push, but pull is more scalable.
- Comment: Downloadable ,installation binary.
- Obser: There is open registry planning group and dev lists available for further discussion
-
ACTIVITIES GOING FORWARD / NEXT STEPS
- Share your feedback and input to:
For more feed back join OR lists and planning group
-Join OpenRegistry Development list openregistry-dev@lists.jasig.org
If slides are used in the session, please ask presenters to convert their slides to PDF and email them to acamp-info@incommon.org
Thank you!