[ncc-services-wg] [ncc-announce] [service] Request for feedback about the new RIPE NCC Access Single Sign-On solution

+1

I've ran into this situation before, working for a company that managed
several LIRs.  I normally didn't have to modify several of the LIRs at
the same time, but occasionally I had to and then it was a pain.

-peter


On 2022 Mar 31 (Thu) at 17:09:35 +0200 (+0200), Theodoros Polychniatis wrote:
: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
:
:On 29/03/2022 10:53, Harry Cross wrote:
:> 
:> Hi Theodoros,
:> 
:> Thank you for your email.
:> 
:> 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.
:> 
:> 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:
:> 
:> 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.
:> 
:> 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.
:> 
:> Thanks
:> 
:> Harry
:> 
:> *From: *ncc-announce <ncc-announce-bounces at ripe.net> on behalf of
:> Theodoros Polychniatis <tpolychnia at ripe.net>
:> *Date: *Tuesday, 29 March 2022 at 09:34
:> *To: *ncc-announce at ripe.net <ncc-announce at ripe.net>
:> *Subject: *[ncc-announce] [service] Request for feedback about the new
:> RIPE NCC Access Single Sign-On solution
:> 
:> 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
:> (https://access.ripe.net).
:> 
:> 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 tpolychnia at ripe.net.
:> 
:> Kind regards,
:> 
:> Theodoros
:> 
:> --
:> Theodoros Polychniatis
:> Asst. Manager Software Engineering
:> RIPE NCC
:> 

:-- 
:
:To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/


-- 
"Gee, Toto, I don't think we are in Kansas anymore."