Resource set registration should be initiated by the resource server. I think in the next version we removed the ability to add a resource set via the GUI.
Before you make a big investment in UMA 1.01, you should really just wait for UMA 2.
If you want to get a head start, you should read the two specs:
- [Federated Authorization for User-Managed Access (UMA) 2.0](https://docs.kantarainitiative.org/uma/ed/oauth-uma-federated-authz-2.0-06.html)
- [User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization](https://docs.kantarainitiative.org/uma/ed/oauth-uma-grant-2.0-06.html)
UMA grant is from the client perspective. UMA Federated Authz covers the RS and AS.
But unfortunately, it doesn't pay to do a deep dive into UMA 1.0.1, which we're removing in 3.2 (not even deprecating).