> On Sep 23, 2024, at 12:07 PM, Brian Demers <[email protected]> wrote:
>
> Exactly!
>
> A little while back, I started re-familiarizing myself with ApacheDS, the
> LDAP API, and trying to do a basic mapping of an inetOrgPerson -> SCIM
> object, and then something else popped up and distracted me.
>
> We could probably also start out with a more _limited_ SCIM server too,
> start with supporting just users, then add groups, then possibly add
> support for various extensions (Enterprise users, etc)
>
> My gut is telling me we should stick this in a separate repo, until we have
> something that is demo-able, though maybe a longer lived branch in SCIMple
> would work too (there shouldn't be any merge conflicts, if we add a new
> module in the. `scim-server-examples` folder.)
>
Could be a Github project as a proof-of-concept. Once it begins to take shape,
we’d have a better idea where it should land.
Lots of code can be harvested from the LDAP API (examples), fortress
(framework) and other places to speed things along.
But, I’d like to have a design in place.
What shape do the APIs take? Will it be an SPI, utility, service, ???
I’m fuzzy on what the interactions are. Some use cases would help me understand
better. In the old days I’d ask for sequence diagram. It could be an image
taken from a whiteboard.
Speaking of, perhaps we have meeting to discuss. The Directory has a Slack
channel. A higher bandwidth discussion to speed things along.
—
Shawn
> I'd love to hear other thoughts/opinions (and what would work best for
> other folks)!
> e.g. we could potentially use this project as a showcase example for other
> Directory projects (which might hint at a separate repo)
>
> Or maybe there is a favored schema we should target first 🤷
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
