Kuadrant / testsuite

3 stars 13 forks source link

Use uma_well_known endpoints in Rego Policy #414

Closed trepel closed 3 months ago

trepel commented 3 months ago

Overview

This is a further improvement of https://github.com/Kuadrant/testsuite/pull/412

Instead of having several endpoints hard-coded the well known endpoints are used.

What was done

All the hard-coded endpoints replaced with endpoints from uma_well_known Client ID and secret got differently so that rego_policy fixture is not dependent on keycloak fixture directly The rego_policy and authorization fixtures moved a bit down after owner_uma fixture since these two now defends on owner_uma. Removal of # pylint: disable=line-too-long

Verification Steps

Eye review, run the test to see that it passes