feat: add required scopes configuration property to openid-connect plugin

[csotiriou]

Fixes #10352

This adds the optional required_scopes configuration property in the openid-connect plugin configuration. In cases where the introspection endpoint of the OIDC server is called, the plugin will check if all required scopes are present in the scopes returned by the introspection endpoint.

I have also updated the documentation to reflect this, in case anyone finds this PR valuable.

[moonming]

@csotiriou thanks for this PR. It will be great if you can add test cases for it :)

[csotiriou]

Hello @moonming I'm trying to wrap my head around the test implementation, my familiarity with lua is limited. However, I have reached the point where I'm making a sample test.

I noticed that for the openid-connect plugin there are some sample oidc providers with a dummy client-id and client-secret used. Must I use the same and have the same configuration in my keycloak? If not, how are tests going to pass during automation?

[moonming]

@Revolyssup Please check how to write a more appropriate test case. I am not familiar with this plug-in.

[Revolyssup]

@moonming @csotiriou I have added the test case and fixed the lint tests to save time.

[moonming]

@csotiriou thanks for your great work 👍

[soulbird]

I think you need to add a test case for scope validation

[Revolyssup]

I think you need to add a test case for scope validation

@soulbird Do you mean the case where the correct scope is passed and the request succeeds?

[moonming]

Conflicting files
docs/en/latest/plugins/openid-connect.md

@csotiriou please fix this when you have time.

[soulbird]

I think you need to add a test case for scope validation

@soulbird Do you mean the case where the correct scope is passed and the request succeeds?

yes

[csotiriou]

Conflicting files
docs/en/latest/plugins/openid-connect.md

@csotiriou please fix this when you have time.

Thanks for the notification, @moonming , It seems that the merge conflicts in the conflicting documentation files have been resolved by @Revolyssup faster, thank you for the help!