What's up with the URL prefixes (mice, alis, etc)?

Feedback General Feedback
,
1

Just because I’m very curious… What’s up with the URL prefixes on the SpConfig endpoint?

exportUrl           : @{url=alis://lifecycleStates/lifecycleStates/export; query=}

resolveByIdUrl   : @{url=mice://v3/identities/$id; query=}

exportUrl           : @{url=shelby://identity-object-configs/identity-object-configs/export; query=}

I love them, btw. More products need to use mice:// as a URL scheme.

2

They’re usually just complicated acronyms. Mice is is the identities service (I believe the I is for identities), and Shelby is the accounts service. Nothing top secret here!

2 Likes
3

These are references to microservices which handle certain import, export, and lookup functionality. ConfigurationHub (sp-config) coordinates actions across a variety of microservices, as you’d expect.

Beyond this, you may also see these names in private APIs behind certain user interfaces for newly created functionality too. Often these launch before a new beta APIs are launched. The private APIs allow our developers to iterate in an early access fashion without having to be locked into a versioned API, even if it is beta.

Nothing to worry about!

2 Likes
4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.