3 Oct
2022
3 Oct
'22
3:27 a.m.
Hi,
Well, don't really see a whole lot I can contribute; this is one of the better spec
docs I've seen in a LONG time. So great work there.
On the topic of extensibility, one area I didn't see a lot of information on was
identity and access management (or IAM). Not sure what you plan on using for your
underlying user system, but you might consider SAML IdP for a base, if not OID; and/or
featuring SAML SP so you can interface third-party identity providers, to facilitate your
onboarding with other institutions, i.e. education, and enterprise organizations) for
supporting third-party login providers. If you decide to support SAML, I would encourage
you to start with Shibboleth (either as a SP, IdP, or both) as a means of jumpstarting
your enrollment into the InCommon Federation as well.
You'll also be doing yourself a favor when you can onboard third-party commercial
products (cloud-hosted or on-premise) which also support SSO with SAML to offload
development cost of those services (i.e. project management, email, CRMs, support ticket
systems, etc.) esp. if you start scaling out your internal "workforce" with
additional volunteers sourced from your existing user base.
That's about all I can think of for now.
Thanks,
Matt (KE7INI)
------- Original Message -------
On Tuesday, September 27th, 2022 at 2:37 PM, Rosy Schechter - KJ7RYV via 44net
<44net(a)mailman.ampr.org> wrote:
Hello 44Net!
For quite some time, y'all have heard rumblings of a new portal, which
Chris has been working on bit by bit. Realizing that it's likely a
larger project than we initially thought, earlier this year the TAC took
on the task of writing a feature requirements document. This has been
the bulk of their work this year so far, and I'm really proud of the
results, which were completed just a couple weeks ago.
I'm writing on behalf of the TAC to share this document with you and to
request comments and comments:
https://www.ampr.org/wp-content/uploads/2022-09-Portal-Features-Requirement…
Ideally, please share your thoughts in this channel rather than emailing
directly, though of course we will read any feedback you send. Pierre,
the TAC Chair, will be watching the list and answering any questions
that may come up.
Note that this document is a feature requirements document - which
outlines the features that the portal needs to have before it's
considered "done." By definition, it's not an engineering document;
we've purposefully not specified the exact technology we'll use to build
this out. We have, however, specified that it will be released as an
open source project as soon as we have a functional version, likely
without all features present. Ultimately this will be a project managed
by our new Director of Technology (who starts on Monday; will introduce
after he starts) and the team he assembles to carry out the build. Thus,
information like timelines, project plans, and database specifications,
etc., will follow his review of this document and any comments from this
group.
And with that, I say - happy reading! And thank you so much for your
thoughts and questions.
Looking forward,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org