Not able to retrive the created entity: 401 unauthorised

[radhay-samagra]

I have registered one schema and added an entity for the same with the following response

Schema:

{
	"$schema": "http://json-schema.org/draft-07/schema",
	"type": "object",
	"properties": {
		"board-hp": {
			"$ref": "#/definitions/board-hp"
		}
	},
	"required": ["board-hp"],
	"title": "board-hp",
	"definitions": {
		"board-hp": {
			"$id": "#/properties/board-hp",
			"type": "object",
			"title": "samarth-hp schema",
			"required": ["name", "phoneNumber", "email"],
			"uniqueIndexFields": ["phoneNumber", "email"],
			"properties": {
				"name": {"type": "string"},
                "phoneNumber": {"type": "string"},
                "email": {"type": "string"}
			}
		}
	},
	"_osConfig": {
		"ownershipAttributes": [
			{
                "email": "/email",
                "mobile": "/phoneNumber",
                "userId": "/phoneNumber"
              }
		],
		"inviteRoles": ["anonymous"],
		"enableLogin": true
	}
}

API Request to create entity

curl --location --request POST \
--header 'content-type: application/json' \
--data-raw '{
    "name": "test-hp",
    "phoneNumber": "1234567890",
    "email": "[email protected]"
}'\
'http://localhost:8081/api/v1/board-hp/invite'

where board-hp is the name of the entity

Response

{
    "id": "sunbird-rc.registry.invite",
    "ver": "1.0",
    "ets": 1651062273207,
    "params": {
        "resmsgid": "",
        "msgid": "8a7054fe-810b-4099-bfed-1859e065dc6e",
        "err": "",
        "status": "SUCCESSFUL",
        "errmsg": ""
    },
    "responseCode": "OK",
    "result": {
        "samarth-hp": {
            "osid": "1-72d3a4e2-4f37-4ec9-867d-be7748018885"
        }
    }

Now I wanted to retrieve my entity via API GET /api/v1/{entity-type}/{id} HTTP/1.1

I made the following request after successfully authenticating as an entity and generated an access token:
access-token: eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJWek9OWUU0TEdObHh1WS1leHdCbmk0Z0tTWmNUaXVaSmlKdF9QeGpyQ01BIn0.eyJleHAiOjE2NTEwNjQyMTAsImlhdCI6MTY1MTA2MzYxMCwianRpIjoiMmI4MzQ0ZTctMjI0My00NmFlLWIwMGUtNWI5MDJiNDFhYTRkIiwiaXNzIjoiaHR0cDovL2xvY2FsaG9zdDo4MDgwL2F1dGgvcmVhbG1zL3N1bmJpcmQtcmMiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZGFiMDg1MjQtNmY2NC00ZTlkLWIzNmEtNjJhMjU3YmEyOGI3IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoicmVnaXN0cnktZnJvbnRlbmQiLCJzZXNzaW9uX3N0YXRlIjoiYWQzMDg0OGYtMzI5Yy00N2U5LTgzODYtYWZlNjU4YzkwZTQyIiwiYWNyIjoiMSIsImFsbG93ZWQtb3JpZ2lucyI6WyJodHRwczovL2xvY2FsaG9zdDo0MjAyIiwiaHR0cDovL2xvY2FsaG9zdDo0MjAyIiwiaHR0cHM6Ly9sb2NhbGhvc3Q6NDIwMCIsImh0dHBzOi8vbmRlYXIueGl2LmluIiwiaHR0cDovL2xvY2FsaG9zdDo0MjAwIiwiaHR0cDovL25kZWFyLnhpdi5pbiIsImh0dHA6Ly8yMC4xOTguNjQuMTI4Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIiwiZGVmYXVsdC1yb2xlcy1uZGVhciJdfSwicmVzb3VyY2VfYWNjZXNzIjp7ImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2UtYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sInNjb3BlIjoicHJvZmlsZSBlbWFpbCIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoiMTIzNDU2Nzg5MCIsImVudGl0eSI6WyJzYW1hcnRoLWhwIl0sImVtYWlsIjoidGVzdEBleGFtcGxlLmNvbSJ9.Fw8BV_QnUedyTF-uK3cGpBCLc0NCmugyfMSkvMY_fdMe43MzhZgTMbKUt4nr05x19Vl9iCRI55YRMhAJ82NX5q-femAxtrdj8FuXEpxak4VBEXH3SmsfD95X5LrokcMfoHpL-qeZtQy3tF9LwUVgEH7KOP0JiQYfimjXNdUgI48nta_rikIqp2PsgN6TVCWzkOKXduZBtdCnMt6kqXod8luAjckfxwKukqgzs4I2hIagkisiL_pupLadDkX0WON0yB53qChDsHCZb2FFc-qL0XOGOP9nAm4mKBrrLlg4jmuEhKWG-5myUS1QSrJBDQktB5cDMpBvBQB3Fy1ml7YC9w

curl --location \
	--request GET \
	--header 'content-type: application/json' \
	--header 'authorization: bearer {access-token}' \
	'http://localhost:8081/api/v1/board-hp/1-d5408ef9-f6b6-47f3-a334-ba85eaaf141a'

I am getting 401 as an HTTP response and I am also not able to find any significant logs by the service to debug.

[tejash-jl]

@radhay-samagra
I think you got the keycloak token by calling http://localhost:8080/auth/realms/sunbird-rc/protocol/openid-connect/token,
instead, can you use http://keycloak:8080/auth/realms/sunbird-rc/protocol/openid-connect/token and also add the

127.0.0.1	keycloak

to /etc/hosts

[gamemaker1]

I'm sorry, there does not seem to be any error here either.

One more question though: has this registry been setup with consent enabled?

[radhay-samagra]

No consent is disabled. I cross checked on the keycloak admin dashboard too

[gamemaker1]

Then I'm not sure what the error could be; I'll try setting up a registry myself tomorrow and debug the problem.

[radhay-samagra]

I can help you with the boilerplate and the configs I have used for replicating the issue on discord.

[gamemaker1]

Yes please, that would be very helpful

[tejash-jl]

@radhay-samagra,
403 issue occurs if authorized user tries to access other entities,
can you check if the osid you are using in the GET API is the same that you received in the invite API response,
Also you can also use this GET API: http://localhost:8081/api/v1/board-hp without osid

[radhay-samagra]

@tejash-jl There was some issue with the regustry-frontend client. I created a new client kn keycloak and I was able to fetch the entities now. Also forwarding 127.0.0.1 to keycloak was necessary apparently. I thought it would not be that important. My issue is now resolved. Thanks.

[gamemaker1]

Good to hear that. Could you please share the config for the registry frontend client as well as the new client you created, maybe we can find out what the problem was from there (just export realm configuration in keycloak, and share the resultant json file). Thank you