- WG-UMA - mailman.kantarainitiative.org

Draft Minutes of UMA telecon 2021-03-18
by Alec Laws 18 Mar '21

18 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-18 MinutesRoll call Quorum was reached. Approve minutes - Approve minutes of UMA telecon 2021-02-04, <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11> , UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> , UMA telecon 2021-02-25, <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25>UMA telecon 2021-03-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-04> , <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25>UMA telecon 2021-03-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-11> Eve Moves to approve, Andi seconds. Motion Passes! ONC Annual Meeting, UMA Content For a Virtual Booth https://www.healthit.gov/news/events/2021-onc-annual-meeting March 29-30 Deadline for content submitted is Mar 24 Pensions Dashboard, any updates Have an agreed path and licenses Profiles Discussion, relationship manager draft UMA Resource Server Management This document extends [UMA Fedz] in order to specify the interface provided by the RS to the RO for resource management. This is achieved by introducing a Resource Management API which is used by a Resource Manager Client to view available resources and direct the AS to use for protection. ** This API could also allows the RO to - view access history - set direct policy (ie Adrian clause) - establish credentials required in AS, (smarthealth.card) Reqs: - THe RO must authenticate to the RS, in order to authorize access to this API - (this capability of the RS is implied by UMA) - The RO can see a list of resources available at this RS (either protected or not) - The RO can modify the protection of resources (ie which AS to protect) - The RO can see AS's available for protection - can the RO direct the RS to get a PAT from a new AS? This is tricky depending on how PAT's are issued (ie may require end-user redirection) Names: - resource management - resource declaration - available resources - resource access management (RAM) This document introduces the following new concepts: - Resource Management API The API presented by the RS to the Resource Manager. This API is OAuth protected - Resource Management Token (what scope should this Access Token capture?) "uma_management" ### 1.3 HTTP Usage, API Security, and Identity Context - add link between RM API and RM Token The `Resource Management API` allows the Resource Owner to: - View the available resources hosted at this RS, and their current protection - View the UMA Authorization Servers available to be used to protect - Manage the UMA protection of available resources Starting Conditions: - The RS hosts resources for the RO - The RS supports resource protection from an UMA AS - The RS has a UMA PAT at one or more UMA ASs (try to bring this into the profile, not as a starting condition) Step 0 The Resource Manager obtains an OAuth Access Token valid for use at the Resource API. The Access Token must allow the RS to determine the RO's resources. - is there a purpose for NOT the RO to use this interface? Is this 'delegation' too early in Step 1 (Get Info) The RM obtains a list of UMA AS's available for resource protection, and a list of available resources Step 2 (Update Protection) The RM directs the RS to modify the resource protection either - putting an unprotected resource under protection at a specific AS, possibly only registering specific scopes - removing the protection of a resource at an AS. The RS will no longer honor RPTs for this resource from that AS - modify the protection of a resource, such as to add or remove scopes ## Available Resources Endpoint The API available at the available resources endpoint enables the resource manager to have knowledge of the resources hosted by the resource server for the resource owner. ``` [ { "_rs_id" "ABC", "resource_scopes":[ "view", "http://photoz.example.com/dev/scopes/print" ], "description":"Collection of digital photographs", "icon_uri":"http://www.example.com/icons/flower.png", "name":"Photo Album", "type":"http://www.example.com/rsrcs/photoalbum", }, ] ``` Protected Resources ``` [ { "_rs_id" "ABC", "authorization_sever_resource_id" : "_as_id" "authorization_server" : "as_identifier", "registered_scopes" : [ "view" ] }, { "_rs_id" "ABC", "authorization_sever_resource_id" : "_as_id_2" "authorization_server" : "as_identifier_2", "registered_scopes" : [ "view", " http://photoz.example.com/dev/scopes/print" ] } ] ``` /authorization-servers/:id/resources ``` [ { "_rs_id" "ABC", "authorization_sever_resource_id" : "_as_id" "registered_scopes" : [ "view" ] }, { "_rs_id" "ABC", "authorization_sever_resource_id" : "_as_id_2" "registered_scopes" : [ "view", " http://photoz.example.com/dev/scopes/print" ] } ] ``` In dashboard world, rs_id = PeI (pension identifier) - to confirm, is the PeI the same as the as_id? ie is it created by the RS or the AS single person, single resource, single rs: can have multiple resource registration, eg with different scopes Resource = Patient Registered Resource 1: Just the Patient Object Registered Resource 2: The Patient + Sub Objects ### Available Resource Description A registered resource is a JSON document that extends the resource description from [UMA Fedz 3.1 Resource Description](1) with the following parameters: authorization_server OPTIONAL A string identifying the authorization server that protects this resource ** could also be the AS policy uri from resource registration? (1 https:// docs.kantarainitiative.org/uma/wg/rec-oauth-uma-federated-authz-2.0.html#re… ) #### List Available Resource Descriptions #### Update Available Resources Description ## Authorization Server Endpoint The API available at the authorization server endpoint enables the resource manager to view and manage the authorization servers available for resource protection. The resource owner may allow resource protection only through the set of available authorization servers. ***note***: a challenge here is that it's quite difficult for this interface to create a relationship between an AS/RS because how the PAT is issued (ie could be interactive) Currently this is a 'dynamic' API since it conveys information to Alice about whether a specific AS is available for use in other protection APIs (ie is there an active/historical PAT for this AS). If this is static, Alice won't know if she can use that AS for protection THe list of AS's may also be specific to the RO. Bob may have registered AS1, while Alice uses AS2 ### Authorization Server Description #### List Authorization Server Description ``` [ { as_url: "http://authserver_id.ca" has_as_pat: true }, { as_url: "http://authserver_id2.com" has_as_pat: false } ] ``` Cheers, - Alec

1 0

Agenda for UMA telecon 2021-03-18
by Alec Laws 17 Mar '21

17 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-18 Head's up that we are in the 'summertime skew' period where we have already started daylight savings time in NA and it hasn't started everywhere. Please double check your calendars :) Date and Time - *Primary-week Thursdays 6:30am PT* - Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> - United States: +1 (224) 501-3316, Access Code: 485-071-053 - See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar Agenda - Approve minutes of UMA telecon 2021-02-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04> , UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11> , UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> , UMA telecon 2021-02-25 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25> , UMA telecon 2021-03-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-04> , UMA telecon 2021-03-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-11> - ONC Annual Meeting, Virtual Booth Update - Profiles Discussion, relationship manager draft - Pensions Dashboard, any updates - AOB Best, - Alec

1 0

Draft minutes of UMA telecon 2021-03-11
by Alec Laws 11 Mar '21

11 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-11 MinutesRoll call Quorum was NOT reached. Approve minutes - Approve minutes of UMA telecon 2021-02-04, <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11> , UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> , UMA telecon 2021-02-25 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25> Deferred ONC Annual Meeting, UMA Content For a Virtual Booth https://www.healthit.gov/news/events/2021-onc-annual-meeting March 29-30 Need to be available at the Booth for the duration of the day (8-5?), can have an "afk" video. Same content platform at dev days, videos+pdf uploads. Colin/Nancy/Alec will cover the booth. *If you're available to help, please reach out!* Planning to repurpose + modify the first half of the UMA in healthcare webinar <https://kantarainitiative.org/download/uma-21st-century-health-information-…> from summary 2020. Will layer on Kantara in general content (existing + new working groups) + specific ONC value alignment Want to showcase highlight UMA + Identity + Consent Receipt(?). A main Kantara Intro: https://youtu.be/iVyP95_OyCM If you have a demo relevant to health care and want it included, please reach out! Airside may have a relevant demo for healthcare to add. Forgerock has a FHIR + UMA demo to add. Patient Centric Solutions has an identity + UMA demo with ID.me, can show off the transparency (granularity) of sharing. Identos case study will cover their project for Identity + UMA in Ontario. Nancy/Alec will be meeting again next Tuesday at 10AM EDT to iterate on the content, please reach out if you'd like to join in Health care can become confused by the range of identity and authorization offerings. Need to show a clear message about how it works together toward a 'wide' ecosystem to bring these disparate approaches together. UMA can support many types of granularity, by resource but also by sensitivity. The data model is all there with FHIR and UMA can easily apply 'arbitrary' authorization slices over it. Pensions Dashboard, any updates Agreements to reference UMA and link to a Kantara hosted (but not UMA WG) hosted page with the profiles and design documents. Finding the right balance between making it open to serve the procurement needs and properly protect everyone Profiles Discussion, relationship manager Continue discussion on how an RS can get a PAT issued, given that the RO is interacting through a API (not directly at the RS). In the PDP profile, the relationship manger API would be used directly from the AS (co-located with the AS), however this isn't the same in the IDENTOS implementation. RS API needs oauth protection, so the Relationship manager has a valid token directed to the RS Relationship manager API. This is NOT the PAT, since it's aud is the RS not the AS. The relationship manager API is derivative of the Resource Registration API, however it's the available vs already registered resources. GET /authorization_servers → list of registered authorization servers. This is easiest way to avoid the topic... assumes that Alice has previously interacted with the RS to have PATs available. If there is no way for Alice to directly interact with the RS this falls apart. Identos currently avoids by having static RS→AS registration and an RS=RO model for PAT issuance, but don't like this. It's organization custodial model vs the *real* RO who is Alice. Need to separate the resource rights administrator from the actual data subject (RO), in this case it's still not the RS=RO, it's RRA=RO. There are *many* RRA's in the model, the RO is a RRA, the RO can delegate some capabilities to another RRA, the RS may apply policy as an RRA during policy setting or resource disclosure. This layered RRA model get's complicated fast, although it's pervasive in normal B2B2C cases (data subject, controller, processor). All the entities in the system perform AS, RS and sometime RRA functions at different times Summertime Skew Head's up to our non-North American members! Attendees As of October 26, 2020, quorum <http://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 8. (Michael, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve) Voting: 1. Peter 2. Eve 3. Alec Non-voting participants: 1. Tim 2. Colin 3. Nancy Regrets: 1. Ian 2. Ken

1 0

Agenda for UMA telecon 2021-03-11
by Alec Laws 11 Mar '21

11 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-11 UMA telecon 2021-03-11Date and Time - *Alternate-week Thursdays 10:00am PT* - Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> - United States: +1 (224) 501-3316, Access Code: 485-071-053 - See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar Agenda - Approve minutes of UMA telecon 2021-02-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04> , UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11> , UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> , UMA telecon 2021-02-25 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25> , UMA telecon 2021-03-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-04> - ONC Annual Meeting, Virtual Booth Update - Pensions Dashboard, any updates - Profiles Discussion, relationship manager - AOB Cheers, - Alec

1 0

Draft minutes of UMA telecon 2021-03-04
by Alec Laws 04 Mar '21

04 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-04 MinutesRoll call Quorum was NOT reached. Approve minutes - Approve minutes of UMA telecon 2021-02-04, <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11> , UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> , UMA telecon 2021-02-25 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25> Deferred ONC Annual Meeting, UMA Content For a Virtual Booth https://www.healthit.gov/news/events/2021-onc-annual-meeting (free registration for attendees) March 29-30. If you're interesting in helping at the booth or there's any UMA content that you'd like shown related to healthcare use-cases, please reach out to Alec Not clear exactly how the booth works at this time, eg what content we can upload or when we need to be 'available'. Maybe a very short demo (5mins) would works well, advertise as a reason to visit the booth. Pensions Dashboard, any updates Very close, all good news. Have a path forward to address any IPR/license concerns. General question, would Kantara be on the hook for any vulnerabilities caused by profiling or implementations? In dashboard use-case, risk is a Bad user can see Alice's pensions data. Aside from the 'risk profile' of the use-case, the protocol was what is being 'relied' on to secure the resources. However, the protocol creator can't(?) be liable and our license should protect Kantara and the UMA WG(?). The responsible party is the operator or implementor. The protocol can't cover all use cases, and this why best practices and implementers guides are provided in addition to the core specs. The current licensing conversation is about confirming that Kantara and/or Origo can't prevent the open use of UMA and the specific profile by the implementors in the Dashboard Program. Kantara need to balance that need with our needs to protect ourselves from the above. There are specific objections to the RAND policy. Should UMA consider changing its IPR? Quite difficult to do for an open group given all the previous contributions. There has been some 'transfer' of ownership between Kantara WGs with different IPR policies (RAND → NAC(?)). Had to get all the contributors to the original WG to agree to this. Is there something Kantara can do to better support this program (and hopefully all the new UMA WG members)? For example, revive the UMA test-suite conversations? Part of the challenge with the UMA test suite is how broad the cases are, maybe a test suite around this specific profile reduces that scope to get this off the ground. There is a demo AS that implements a proof of concept of the pensions dashboard (~2018), any further assistance that could be offered to the PDP would need to be based on the new iteration of the profile. However, this would be a first step to build a PDP RS conformance suite? .Our test suites should have specific 'modes' for the different profiles (HEART, PDP) UMA/Email proof-of-concept https://github.com/uma-email/poc Igor was able to respond to some of our questions from last week: https://kantarainitiative.org/pipermail/wg-uma/2021-March/006124.html Profiles Discussion, relationship manager Is there any purpose for a single RS to be protected by many ASs? For different RO's: yes. Is there any purpose for a single RS to be protected by many ASs for a single Resource Owner? These use-cases are more 'theoretical', and there is no limitation in the core UMA design. Maybe the RS would only support specific AS's for certain resources (eg high sensitivity) How would a RS get a RO specific PAT in this mode? RS must be a client of the AS. PAT protects an 'offline' API, so there is preference to a long-lived token to reduce the frequency that Alice must re-establish the relationship. The more AS's a RS is registered at for Alice, the more she'll have to re-establish the PAT. PFS@AS → RS: AT, access token with demographics (JWT) Is this a discovery mechanism at the RS? RS → AS: POST /token body = AT AS --> RS: PAT So in this use case, the AS "tells' the RS to get a PAT. Attendees As of October 26, 2020, quorum <http://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Michael, Karim, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve) Voting: 1. Alec 2. Eve 3. Michael 4. Domenico Non-voting participants: 1. Nancy 2. Scott 3. Tim 4. Ian 5. Colin

1 0

Agenda for UMA telecon 2021-03-04
by Alec Laws 03 Mar '21

03 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-03-04 Date and Time Primary-week Thursdays 6:30am PT Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> United States: +1 (224) 501-3316, Access Code: 485-071-053 See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar <http://kantarainitiative.org/confluence/display/uma/Calendar> Agenda Approve minutes of UMA telecon 2021-02-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>, UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11>, UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18>, UMA telecon 2021-02-25 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25> Pensions Dashboard, any updates UMA/Email proof-of-concept Profiles Discussion, relationship manager AOB Best, - Alec

1 0

Draft Minutes for UMA telecon 2021-02-25
by Alec Laws 02 Mar '21

02 Mar '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25 Minutes Roll call Quorum was NOT reached. Approve minutes Approve minutes of UMA telecon 2021-02-04, <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11>, UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> Deferred Pensions Dashboard, any updates All positive. No major changes, IPR issues are progressing. PDP may contribute their profiles directly to 'Kantara' (ie not the WG) to avoid challenges with the RAND license UMA continues to be required by the program UMA/Email proof-of-concept https://github.com/uma-email/poc <https://github.com/uma-email/poc> How does this compare with existing 'secure messaging' products? This is made to ride onto of the existing SMTP/IMAP protocols. There is a POC/demo available here: https://www.federizer.org/ <https://www.federizer.org/> Is there a path to having this attachment protocol as an extension to the existing SMTP protocol <https://tools.ietf.org/html/rfc5321>? Would have to work through IETF. Do the two mail services both have to support the extension? likely yes, maybe need a discovery mechanism. If the recipient doesn't support could fallback from claims pushing to interactive claims gathering. However, this pushes the RqP authentication question as the senders AS would need to allow federation to the RqP email domain. This could use the 'Trusted Claims" profile, however there is no standard way that a mail server must authenticate the user? ie not all are OIDC providers. This would need further exploration. Profiles Discussion, relationship manager Three "real" use cases to design around A resource server that holds Alice's data, however does not have an end-user authentication mechanism. A resource server that can authenticate Alice (somehow), and wants to offer resource managed integrated in other client applications FPX profile: the RS offers an OAuth API to authenticate the end-user, the RS like (1) would federate to another IDP (Trusted Claims??) PDP profile: The RS offers an AT protected 'find' API. The AS, after getting Alice's consent, hits the find API with Alice's verified claims, packaged in the AT, at every registered Pension Provider RS. If the RS has pensions for Alice, it needs a PAT to start registering resources with. It "exchanges" the AT provided by the PFS with the AS for a RS-audience PAT. The RS can then register the found pensions. Since the RS and the AS are in a secure eco-system and the RO is authenticated to the AS at the time of the resource discovery , the RS can use temporary credentials specific to the RO at the AS to obtain the PAT. It is proposed that the AS will issue an authorization token for use by the RS for grant type "urn:ietf:params:oauth:granttype:jwt-bearer" as in [RFC7523] Section 2.1 Can to two interactions use the same APIs mechanisms? GET /resources → returns available resources for Alice \{ as defined by UMA Fedz with the addition of an optional "authorization_server" attribute, which points to the specific AS this resource is currently registered with } POST /resource/_id/ \{ at_as: url_to_my_AS } GET /authorization_servers → return list of supported authorization servers, either for Alice or in general This is where the intersection between UMA (API based resource) and w3c VC issuance starts to work. GET /resources == GET /credential offers, POST /resource_to_as = issue me this credential. This also comes around to wallet = personally controlled UMA AS. How can we design to support many Authorization Servers (ie a wide-ecosystem!)? The PFS was built to not exclude many AS's. A AS's would be hosted out of the gate, however the expectation is towards the more "open-finance" model where many Financial Institutions would host an AS for their customers/users. The 'governance registry' (as specified in the report) and federated identity service becomes the common trust sources for the ecosystem. How woudl pension rsources previously registered at one AS, be moved to a second one? What if the AS is the 'gateway' to the service where Alice wants to make her pension available Attendees As of October 26, 2020, quorum <http://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Michael, Karim, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve) Voting: Micheal Alec Non-voting participants: Scott Ken Ian Anik Nancy Colin Regrets: Eve Andi

2 3

Re: [WG-UMA] AEMS in less than 300 words
by Ilyah Simuni 25 Feb '21

25 Feb '21

Igor, Interesting idea for AEMS implementation. Wondering if you have done threat modeling on this architecture. I see a lot of potential attack vectors that might break the protocol. One concern is that the policy is separate from the email, so enforcement must be coded in the exchange protocol, which might not work as intended. Regards, ilyah -----Original Message----- From: WG-UMA <wg-uma-bounces(a)kantarainitiative.org> On Behalf Of wg-uma-request(a)kantarainitiative.org Sent: Thursday, February 25, 2021 10:46 AM To: wg-uma(a)kantarainitiative.org Subject: WG-UMA Digest, Vol 140, Issue 13 Send WG-UMA mailing list submissions to wg-uma(a)kantarainitiative.org To subscribe or unsubscribe via the World Wide Web, visit https://kantarainitiative.org/mailman/listinfo/wg-uma or, via email, send a message with subject or body 'help' to wg-uma-request(a)kantarainitiative.org You can reach the person managing the list at wg-uma-owner(a)kantarainitiative.org When replying, please edit your Subject line so it is more specific than "Re: Contents of WG-UMA digest..." Today's Topics: 1. Agenda for UMA telecon 2021-02-25 (Alec Laws) 2. AEMS in less than 300 words (Igor Zboran) ---------------------------------------------------------------------- Message: 1 Date: Thu, 25 Feb 2021 08:38:15 -0500 From: Alec Laws <malcolm.laws(a)gmail.com> To: "wg-uma(a)kantarainitiative.org WG" <wg-uma(a)kantarainitiative.org> Subject: [WG-UMA] Agenda for UMA telecon 2021-02-25 Message-ID: <DD680E9B-5818-4335-AAC1-D970D34D4233(a)gmail.com> Content-Type: text/plain; charset="us-ascii" https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25 UMA telecon 2021-02-25 Date and Time Alternate-week Thursdays 10:00am PT Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> United States: +1 (224) 501-3316, Access Code: 485-071-053 See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar <http://kantarainitiative.org/confluence/display/uma/Calendar> Agenda Approve minutes of UMA telecon 2021-02-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>, UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11>, UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> Pensions Dashboard, any updates UMA/Email proof-of-concept Profiles Discussion, relationship manager AOB - Alec

2 1

AEMS in less than 300 words
by Igor Zboran 25 Feb '21

25 Feb '21

Hi UMAnitarians, Please see the attached document. It is an excerpt from the upcoming draft-01. Regards -Igor

1 0

Agenda for UMA telecon 2021-02-25
by Alec Laws 25 Feb '21

25 Feb '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-25 UMA telecon 2021-02-25 Date and Time Alternate-week Thursdays 10:00am PT Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> United States: +1 (224) 501-3316, Access Code: 485-071-053 See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar <http://kantarainitiative.org/confluence/display/uma/Calendar> Agenda Approve minutes of UMA telecon 2021-02-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-04>, UMA telecon 2021-02-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-11>, UMA telecon 2021-02-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-02-18> Pensions Dashboard, any updates UMA/Email proof-of-concept Profiles Discussion, relationship manager AOB - Alec

1 0