> > V 2.5 Security and new RDB$ADMIN role:
> > The release notes say:
> > Syntax Patterns
> > The SYSDBA, or a user with SYSDBA privileges in both the current
> > database and the security database, can add a new user:
> >
> > I can imagine that the GRANT will provide this privilege on the
> > current database. But can anyone tell me how you grant against the
> > security database in exclusion of the current database?
>
> With gsec.
>
> With regards,
>
> Thomas Steinmaurer

So we've gone from GSEC + ServicesAPI where the latter was the preferred
option for user management where we didn't want to shell out to gsec for
normal user creation/deletion/editing (i.e I've been (able to) avoid the use
of GSEC completely for years.
To
Standard SQL (or sort of) and being stuck with returning to GSEC for the
admin upscaling. So we still need to shell out to GSEC.

Hopefully this is an intermediate step cause it's not become easier, it's
become more fragmented, (GSEC, SQL and ServicesAPI). Pity we couldn't have
at least provided a services API change for the admin uplift.
Alan