1. Create a Basic Resource Server

🌟 key concept a resource server docid\ nwlnjrwf4grax mlil8de is a server that hosts protected resources that can be accessed over the web through the resource server's api this example setup demonstrates how to create a basic resource server using the identos authorization server todo add overview diagram with step emphasized this setup will use a fake resource server that todo introduce example prerequisites if you'd like to try this setup yourself, please note the following assumptions you should have admin access to an identos authorization server that's already installed and running (this should already be setup for you) you should know how to make api calls using curl (client url command line utility) each step involves making one or more api calls to the authorization server for each api call, you'll need to replace the following placeholders with the right values according to your authorization server's configuration placeholder description example value {{as url}} the base url of your authorization server http //localhost 9091 {{as admin uri}} the uri of your authorization server's admin api in most cases, this uri will end with /json api http //localhost 9091/json api {{as admin static token}} a static authorization token for accessing your authorization server's admin api c96584c7 05ca 4df3 b935 98a4fc7d7bbc not sure about something? don't worry, we've got you covered! visit our learn the basics docid\ zfok8uffunxjssg p5bdf section to explore key concepts and articles, or contact support for help with your identos configuration each step will also guide you through related concepts step by step setup to create a resource server in the authorization server, we need to define the resource server as an oauth client in the authorization server create the resource server record in the authorization server for our example, we'll create a resource server named patient resource server that's accessible at the url https //patient rs fakehospital com for simplicity, we'll assume that the resource server has a clientsecret of badpassword for a full explanation of each operation and its parameters, see create a resource server docid 4zq ogxlxrhtewfzqur9b define the resource server as an oauth client run the admin api call below to define the patient rs resource server as an oauth 2 0 client in the authorization server's oauth client metadata and oauth client databases since this will be the first oauth client in our authorization server, the blood glucose app will be id = 1 in both databases curl location g request patch '{{as admin uri}}' \\ \ header 'content type application/vnd api+json; ext=jsonpatch' \\ \ header 'authorization {{as admin static token}}' \\ \ header 'apiversion v1 0' \\ \ header 'accept language en' \\ \ data raw '\[ { "op" "add", "path" "/oauth client metadata", "value" { "id" 1, "type" "oauth client metadata", "attributes" { "issueruri" "https //patient rs fakehospital com/", "clientauthenticationtype" "client secret basic", "clienttype" "confidential", "granttypes" "refresh token client credentials", "jwksraw" null, "jwksuri" null, "scopes" "uma protection", "clientsecret" "badpassword" } } }, { "op" "add", "path" "/oauth client", "value" { "type" "oauth client", "id" 1, "attributes" { "clientid" "patient rs", "clientname" "patient resource server" }, "relationships" { "oauthclientmetadata" { "data" { "type" "oauth client metadata", "id" 1 } } } } }, ]' create the resource server record run the admin api call below to also add the patient rs resource server to the authorization server's resource server database, and associate it with the oauth client definition ( id = 1 ) we created for it in the previous step since this will be the first resource server in our authorization server, the patient rs resource server will be id = 1 in the resource server database for a full explanation of each operation and its parameters, see create a resource server docid 4zq ogxlxrhtewfzqur9b curl location g request patch '{{as admin uri}}' \\ \ header 'content type application/vnd api+json; ext=jsonpatch' \\ \ header 'authorization {{as admin static token}}' \\ \ header 'apiversion v1 0' \\ \ header 'accept language en' \\ \ data raw '\[ { "op" "add", "path" "/resource server", "value" { "type" "resource server", "id" 1, "attributes" { "baseurl" "https //patient rs fakehospital com/", "name" "patient resource server", "resourceserverid" "patient rs" }, "relationships" { "oauthclient" { "data" { "id" 1, "type" "oauth client" } } } } } ]' (optional) view the resource server now run the api call below to check if the resource server exists curl location g request get '{{as admin uri}}/resource server/1' \\ \ header 'apiversion v1 0' \\ \ header 'content type application/vnd api+json' \\ \ header 'authorization {{as admin static token}}' \\ \ header 'accept language en' next steps ✅ you just created a basic resource in the authorization server! next step proceed to 2 create a basic resource docid\ ba8inrcxegve9zyr7gjuh to learn how to define a resource within the basic resource server you created learn more read the create a resource server docid 4zq ogxlxrhtewfzqur9b guide to learn more about creating, updating, and managing resource servers in the authorization server