introduce consent screen and custom scopes in mock oauth server

[ondrejtomcik]

No description provided.

[jkralik]

The test fails because you pass the array as a joined string with "," so the scope is not an array as is expected by parser scopes:
https://github.com/plgd-dev/hub/blob/main/pkg/security/jwt/claims.go#L72

[Danielius1922]

Regarding SonarCloud analysis: I usually ignore low coverage if it's caused by negative code paths (ie error handling). However, since mock oauth is an integral part of most of our tests I would keep the coverage analysis enabled and try to keep coverage in the usual 70-80% realm (if possible), so we know it behaves as it should.

[ondrejtomcik]

@Danielius1922 okay. I will do my homework 🙂

[ondrejtomcik]

@Danielius1922 better coverage? :)

[jkralik]

Please update properly MR https://github.com/plgd-dev/www/pull/35

[jkralik]

@ondrejtomcik Did you look at smells (2 critical)?

[Danielius1922]

@Danielius1922 better coverage? :)

Yop, great coverage! Good job.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

89.6% Coverage
0.0% Duplication