<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi Harry, First of all, thank you for the suggestion and also the way you have described it. It helps us better understand what you need and the rationale! I added both items (the account selector and the email under the profile name) to our list of requested features. We will assess all them, and see what is feasible and how. In the meantime, it would be good to see who else in the list finds these features important, by replying to this thread. Best regards, Theodoros <div class="moz-cite-prefix">On 29/03/2022 10:53, Harry Cross wrote: </div> <blockquote type="cite" cite="mid:CWXP123MB571634238288DEF130649C7CA71E9@CWXP123MB5716.GBRP123.PROD.OUTLOOK.COM"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)">  <style>@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:10.0pt; font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}span.EmailStyle19 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;}div.WordSection1 {page:WordSection1;}</style> <div class="WordSection1"> Hi Theodoros,<o:p></o:p> Thank you for your email.<o:p></o:p> <o:p> </o:p> I’m an IT contractor who now works with a few different entities who are all RIPE members and have separate accounts in the portal/SSO.<o:p></o:p> <o:p> </o:p> If possible (and I suspect this might be a tricky integration to get right), I’d like to see a way (much like Google) where I can be signed into multiple RIPE accounts at once and then easily switch between them via a drop down in the menu under my name:<o:p></o:p> <o:p> </o:p> <img style="width:3.2291in;height:2.5937in" id="Picture_x0020_1" src="cid:part1.4XjSAh4a.Ro5Nvas0@ripe.net" class="" width="310" height="249"><o:p></o:p> <o:p> </o:p> Instead of just providing “Log out”, there could be a list of all the entities to which I am attached there and the option to switch to/log out of each entity (and of course add a new entity). I do think there would then need to be a clear message somewhere to state which entity is being looked at to prevent incorrect changes being made to the wrong organisation. <o:p></o:p> <o:p> </o:p> I do suspect this isn’t something that will be amazingly popular, but it’s an issue I’ve been caught up on a couple of times – the other option would be to maybe add the email address to the name line if that would be easier to integrate.<o:p></o:p> <o:p> </o:p> Thanks<o:p></o:p> <o:p> </o:p> Harry<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: ncc-announce <a class="moz-txt-link-rfc2396E" href="mailto:ncc-announce-bounces@ripe.net"><ncc-announce-bounces@ripe.net></a> on behalf of Theodoros Polychniatis <a class="moz-txt-link-rfc2396E" href="mailto:tpolychnia@ripe.net"><tpolychnia@ripe.net></a> Date: Tuesday, 29 March 2022 at 09:34 To: <a class="moz-txt-link-abbreviated" href="mailto:ncc-announce@ripe.net">ncc-announce@ripe.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:ncc-announce@ripe.net"><ncc-announce@ripe.net></a> Subject: [ncc-announce] [service] Request for feedback about the new RIPE NCC Access Single Sign-On solution<o:p></o:p> </div> <div> Dear colleagues, At the RIPE NCC we are constantly working to improve the security of our services, both internal and external. This is reflected in the work we have planned for our business applications in the coming period, specifically the modernisation of RIPE NCC Access (<a href="https://access.ripe.net" moz-do-not-send="true" class="moz-txt-link-freetext">https://access.ripe.net</a>). RIPE NCC Access is the Single Sign-On (SSO) solution that we use to authenticate and authorise users to access our applications. It is a combination of a third-party identity provider and an application that we have developed in-house. Thanks in part to the feedback we have received over the past few years, we have identified several issues with the current solution and, in response, we have begun to review its architecture and assess possible improvements. We would like to involve our community early and ask for your feedback on this topic. Are there any features that you think are important for our SSO solution? What are you missing in the current solution? We value your feedback and look forward to hearing from you! You can share your ideas either by posting them on the ncc-services mailing list or by sending me an email at <a class="moz-txt-link-abbreviated" href="mailto:tpolychnia@ripe.net">tpolychnia@ripe.net</a>. Kind regards, Theodoros -- Theodoros Polychniatis Asst. Manager Software Engineering RIPE NCC <o:p></o:p> </div> </div> </blockquote> </body> </html>