Add Okta example to JWK URL

v2.5/auth/validator.json

@@ -48,11 +48,12 @@
         "jwk_url": {
             "$id": "#auth/validator/jwk_url",
             "title": "JWK URL",
-            "description": "The URL to the JWK endpoint with the public keys used to verify the token's authenticity and integrity. Use with `cache` to avoid re-downloading the key on every request. Consider enabling [shared caching](/docs/authorization/jwk-caching/) too. The identity server will receive an HTTP(s) request from KrakenD with a KrakenD user agent.\n\nSee: https://www.krakend.io/docs/authorization/jwt-validation/",
+            "description": "The URL to the JWK endpoint with the public keys used to verify the token's authenticity and integrity. Use with `cache` to avoid re-downloading the key on every request. Consider enabling [shared caching](/docs/authorization/jwk-caching/) too. The identity server will receive an HTTP(s) request from KrakenD with a KrakenD user agent, and the identity server must reply with a JSON object and a content-type `application/jwk-set+json` or `application/json`.\n\nSee: https://www.krakend.io/docs/authorization/jwt-validation/",
             "type": "string",
             "examples": [
                 "https://some-domain.auth0.com/.well-known/jwks.json",
-                "http://KEYCLOAK:8080/auth/realms/master/protocol/openid-connect/certs"
+                "http://KEYCLOAK:8080/auth/realms/master/protocol/openid-connect/certs",
+                "https://yourOktaBaseUrl/v1/keys"
             ]
         },
         "jwk_local_path": {
@@ -144,7 +145,7 @@
         "roles_key": {
             "$id": "#auth/validator/roles_key",
             "title": "Roles key",
-            "description": "When validating users through roles, provide the key name inside the JWT payload that lists their roles. If this key is nested inside another object, add `roles_key_is_nested` and use the dot notation `.` to traverse each level. E.g.: `resource_access.myclient.roles` represents the payload `{resource_access: { myclient: { roles: [\"myrole\"] } }`.\n\nSee: https://www.krakend.io/docs/authorization/jwt-validation/",
+            "description": "When validating users through roles, provide the key name inside the JWT payload that lists their roles. If this key is nested inside another object, add `roles_key_is_nested` and use the dot notation `.` to traverse each level. E.g.: `resource_access.myclient.roles` represents the payload `{resource_access: { myclient: { roles: [\"myrole\"] } }`. Notice that the roles object you choose is a list, not a map.\n\nSee: https://www.krakend.io/docs/authorization/jwt-validation/",
             "type": "string",
             "examples": [
                 "resource_access.myclient.roles"