<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><span><div>Colleagues</div><div><br></div><div>I think we have now agreed on these problem and solution definitions:</div><div><br></div><div>Problem Definition</div><div><br></div><div>LIRs would like a mechanism to easily add/remove users to centralised SSO authentication groups for maintaining objects in the RIPE Database.</div><div><br></div><div><br></div><div>Solution Definition</div><div><br></div><div>Stage 1</div><div><br></div><div>-Non billing Users listed in an LIR´s portal account will be contained in a default authentication group</div><div><br></div><div>-Non billing users added or removed through the portal UI will be automatically adjusted in this group</div><div><br></div><div>-This authentication group can be referenced in MNTNER objects by a new authentication method</div><div><br></div><div>-These authentication groups for LIRs will be stored in a way that updates to the RIPE Database is not dependent on the availability of the portal service</div><div><br></div><div><br></div><div>Stage 2</div><div><br></div><div>-Non billing Users listed in an LIR´s portal account can be added to and removed from user defined SSO authentication groups</div><div><br></div><div>-Each User can be a member of any number of named groups</div><div><br></div><div>-The authentication groups can be configured using the portal UI</div><div><br></div><div>-These groups can be referenced in MNTNER objects by the new authentication method</div><div><br></div><div><br></div><div>The chairs will now ask the RIPE NCC to work from these definitions in preparing their implementation plan.</div><div><br></div><div>cheers</div><div>denis</div><div><br></div><div>co-chair DB-WG</div></span><br></div></div></body></html>