[CO-188] ProvisioningEngineComponent Created: 20/Sep/11 Updated: 24/Feb/13 Resolved: 24/Feb/13 |
|
| Status: | Resolved |
| Project: | COmanage |
| Component/s: | Registry |
| Affects Version/s: | COmanage Registry 0.3 (Basic Shape) |
| Fix Version/s: | COmanage Registry 0.8 (Omnipotent Octagon) |
| Type: | New Feature | Priority: | Blocker |
| Reporter: | Benn Oshrin (internet2.edu) | Assignee: | Benn Oshrin (internet2.edu) |
| Resolution: | Completed | Votes: | 0 |
| Labels: | ligo-external-collaborator, sprint11, sprint12 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Define interim API for calling provisioning scripts. Initial needs are to provision to KDC and maybe LDAP (if it's not hooked up via SQL backend). May also need to assign LIGO IDs. |
| Comments |
| Comment by scott.koranda [ 27/Oct/11 ] |
|
Turn description into a first draft of LIGO requirements. |
| Comment by benno [ 10/Jul/12 ] |
|
As per the diagram at https://spaces.internet2.edu/display/COmanage/Provisioning%20From%20Registry Create a ProvisioningEngineComponent that provides methods like processAddRole(), processDeleteRole(), processChangedAttributes() (or whatever) and invokes ProvisioningComponents. For the initial design, all data will be passed, and it will be up to the ProvisioningComponents to determine what, if anything, to do with it. This is subject to change in the future. |
| Comment by benno [ 24/Feb/13 ] |
|
Initial implementation in r461. |