Re: Proposal: Optional clientId / clientSecret in createPrincipal API for Migration Support

2025-07-15 Thread Arun Suri
ight be worth it to also have a > feature > > > flag to control the new functionality. > > > > > > Re: External IdP - most of the authentication code is already in > `main`. > > > There are a few remaining dangling pieces related to connecting > external >

Proposal: Optional clientId / clientSecret in createPrincipal API for Migration Support

2025-07-08 Thread Arun Suri
et` fields, with the above safeguards in place. We would appreciate your feedback on this proposal and are happy to contribute a patch once there’s alignment. We’re also open to discussing this during the next Polaris Community Sync if helpful. Arun Suri Senior Software Engineer He/him/his Engine

Re: Proposal: Optional clientId / clientSecret in createPrincipal API for Migration Support

2025-07-10 Thread Arun Suri
is exported into a file, which is then imported into the new instance > before it is started for the first time. > > I wonder how your tooling could obtain Principals' secrets from the old > Polaris instance for use as the new Principal creation request parameter. > > Cheers, &g

Re: Proposal: Optional clientId / clientSecret in createPrincipal API for Migration Support

2025-07-14 Thread Arun Suri
Polaris delegate user management to that system. There's some > > existing support for that, but I'm not sure if anyone tried it end-to-end > > without any custom code on the server side (it is certainly possible with > > custom code). > > > > Thanks, > > Dmitr

Re: Proposal: Optional clientId / clientSecret in createPrincipal API for Migration Support

2025-07-16 Thread Arun Suri
nteering to make a PR for this, Arun! Looking forward > > to it. > > > > > > > > As discussed, please consider securing the extra capability via (new) > > > > permission checks. I'd think it might be worth it to also have a > > feature > > &g