Page Comparison

...

Main UMA1 Interop Testing page | Features and Feature Tests | Results | uma-dev listParticipants in UMA1 testing must register on this page, either by editing the page or by contacting the UMA WG chair, and should subscribe

We are planning to do initial interop testing of UMA authorization servers against Roland Hedberg's test suite. Eventually we will test UMA resource servers and clients as well, and conduct cross- matrix testing. In preparation for these later phases, we began to register interop participants on this page; don't read too much into the solution information provided here for now.

Subscribe to the uma-dev mailing list , which is being used for interop-related communications. No ranking of other special meaning should be attached to the order in which participants appear. Participants must fill out their relevant rows in the following tables (or let the WG chair know their information).for updates.

Participant information

...

For the purposes of automating testing, we have agreed one option is to use a query parameter with the name _umaauthn to convey a token string that enables login of an RO or RqP. Any RqP credentials provided in the form of "token strings" below can be used in this fashion.

It is assumed that the C is claims-unaware and will be using the redirect claim profile to redirect the RqP to the AS for login as the sole claims-gathering process.

The "Alice" user can be used as both an RO and an RqP, and the "Bob" user can be used as an RqP. The different RqPs can be used with the same client to test policies that discriminate between RqPs using the same client. Clients "A" and "B" can be easily used to test policies that discriminate between the same RqP using different clients.

...

Solution information: C role

...