Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -6,9 +6,9 @@
6	6
7	7	The first step is for you to **get the developer accreditation**. Contributors can register and manage applications within the Community Apps Catalogue.
8	8
9		-Send an email to [[support@humanbrainproject.eu>>mailto:support@humanbrainproject.eu]] with a short summary of your intentions.
	9	+Send an email to [[support@ebrains.eu>>mailto:support@ebrains.eu]] with a short summary of your intentions.
10	10
11		-The support team will apply the permissions to your user: your account will be upgraded with developers privileges the next time you will login.
	11	+The support team will apply the permissions to your user: your account will be [[upgraded with developers privileges>>doc:Collabs.collab-devs.collaboratory-v2.keycloak.user administration.WebHome]] the next time you will login.
12	12
13	13	(% class="box infomessage" %)
14	14	(((
...	...	@@ -15,39 +15,72 @@
15	15	Only SGA2 accredited users will be automatically granted the developer accreditation.
16	16	)))
17	17
18		-(% class="wikigeneratedid" %)
19	19	== Making your app available to users ==
20	20
21		-In order for you application to be installable by users, it needs to be registered within the [[Community Apps Catalogue>>doc:Apps.WebHome]].
	20	+In order for you application to be installable by users, it needs to be registered within the [[Community Apps Catalogue>>doc:Apps.WebHome]].
22	22
23	23	Once this simple step is complete, users will be able to install your app within their collabs.
24	24
25	25	=== Registering an application in the Catalogue ===
26	26
27		-Navigate to the catalogue and click on **+Create App** in the top right corner. Enter a name for your app and click on **Create**.
	26	+Navigate to the catalogue and click on **+Create App** in the top right corner. Enter a name for your app and click on **Create**.
28	28
29		-Fill the form with the following information:
	28	+Fill the form with the following information:
30	30
31		-* **main URL**: the URL of the homepage of your app. This is where user will be directed when then open your app in a collab.
32		-* **settings URL**: the URL of the your settings management page if you have one.
33		-* **description**: a description of what your app does to help users select it.
34		-* **under development?**: should be checked if you don't want your app to be available by default by other users.
35		-* **category**: a category to help structuring the applications.
36		-* **maintainers**: a list of users who maintain the app. The users need to have logged in the wiki at least once to be found. Maintainers are granted the right to modify an app registration.
37		-* **documentation URL**: if your app has online user documentation, a link will be provided to users when they use your app.
38		-* **repository**: a URL to a public repository so users can check the sources of your app.
	30	+* **main URL**: the URL of the homepage of your app. This is where user will be directed when then open your app in a collab.
	31	+* **settings URL**: the URL of the your settings management page if you have one.
	32	+* **description**: a description of what your app does to help users select it.
	33	+* **under development?**: should be checked if you don't want your app to be available by default by other users.
	34	+* **category**: a category to help structuring the applications.
	35	+* **maintainers**: a list of users who maintain the app. The users need to have logged in the wiki at least once to be found. Maintainers are granted the right to modify an app registration.
	36	+* **documentation URL**: if your app has online user documentation, a link will be provided to users when they use your app.
	37	+* **repository**: a URL to a public repository so users can check the sources of your app.
39	39
40		-Click on **Save**. Your app is now registered and waiting for users to install it!
	39	+Click on **Save**. Your app is now registered and waiting for users to install it!
41	41
42		-=== Installing your app in a collab ===
	41	+=== Installing your app in a collab ===
43	43
44		-1. In order to install your app, you need to navigate to a collab where you have either the **editor** or **administrator** role.
45		-1. Click on **Create**. Enter a title for this instance of your app and select **Community App** in the right selector.
46		-1. Click on **Create**. You will be presented with the Community App Catalogue. The app you will see are the public apps and the ones your a maintainer of.
47		-1. Select your app and click on **Save and View**.
	43	+1. In order to install your app, you need to navigate to a collab where you have either the **editor** or **administrator** role.
	44	+1. Click on **Create**. Enter a title for this instance of your app and select **Community App** in the right selector.
	45	+1. Click on **Create**. You will be presented with the Community App Catalogue. The app you will see are the public apps and the ones your a maintainer of.
	46	+1. Select your app and click on **Save and View**.
48	48
49		-You should now see how your app looks like within a collab.
	48	+You should now see how your app looks like within a collab.
50	50
	50	+== Getting your app instance context ==
	51	+
	52	+Instances of your applications will be installed by collab authors in many different collabs. In order to let you customise the user experience based on its context, the Collaboratory will automatically pass query parameters to your app:
	53	+
	54	+* **##clb-collab-id##**: the unique, human-readable identifier of the collab.
	55	+* ##**clb-doc-path**##: the path of your app instance within the collab. If your app is at the root of a collab, this value will be empty.
	56	+* ##**clb-doc-name**##: the name of the document where your app instance is installed.
	57	+* ##**clb-drive-id**##: the unique identifier of the drive of the collab. This id is required if you want to fetch or store documents within the drive of the collab.
	58	+
	59	+== App settings ==
	60	+
	61	+The app settings are the values the collab author can modify to change the behaviour of your application within her collab.
	62	+
	63	+=== Writing settings ===
	64	+
	65	+The Collaboratory comes with a mechanism to let your app store these settings directly in the Collaboratory.
	66	+
	67	+In order to do that, your app needs to use the [[postMessage javascript API>>https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage]] to send the settings to store to the Collaboratory:
	68	+
	69	+{{code language="javascript"}}
	70	+window.parent.postMessage({
	71	+ topic: '/clb/community-app/settings',
	72	+ data: {
	73	+ setting1: 'setting 1 value',
	74	+ setting2: 'setting 2 value',
	75	+ // ...
	76	+ // reload: false // avoid page reload on settings change
	77	+ }}, 'https://wiki.ebrains.eu');
	78	+{{/code}}
	79	+
	80	+=== Fetching settings ===
	81	+
	82	+The Collaboratory will get the settings from its key/value store and pass them to your app through query parameters.
	83	+
51	51	== Creating your OpenID Connect client ==
52	52
53	53	The steps to create an OpenID Connect client are the following:
...	...	@@ -56,6 +56,8 @@
56	56	1. use the token to call the create endpoint
57	57	1. save your registration access token for further modifications of your client
58	58
	92	+Note that a [[notebook>>https://lab.ebrains.eu/user-redirect/lab/tree/drive/Shared%20with%20all/Collaboratory%20Community%20Apps/Managing%20an%20OpenID%20Connect%20client.ipynb||rel="noopener noreferrer" target="_blank"]] is available to help you create and modify your OIDC client.
	93	+
59	59	=== Fetching your developer access token ===
60	60
61	61	Getting your developer token is done in one simple step: authenticate against the developer client with the password grant.
...	...	@@ -68,11 +68,11 @@
68	68	echo '\nEnter your password' && read -s clb_dev_pwd &&
69	69
70	70	# Fetch the token
71		-curl -X POST https://iam.humanbrainproject.eu/auth/realms/hbp/protocol/openid-connect/token \
	106	+curl -X POST https://iam.ebrains.eu/auth/realms/hbp/protocol/openid-connect/token \
72	72	-u developer: \
73	73	-d 'grant_type=password' \
74		- -d "username=${clb_dev_username}" \
75		- -d "password=${clb_dev_pwd}" |
	109	+ --data-urlencode "username=${clb_dev_username}" \
	110	+ --data-urlencode "password=${clb_dev_pwd}" |
76	76
77	77	# Prettify the JSON response
78	78	json_pp;
...	...	@@ -107,7 +107,7 @@
107	107	clb_dev_token=...
108	108
109	109	# Send the creation request
110		-curl -X POST https://iam.humanbrainproject.eu/auth/realms/hbp/clients-registrations/default/ \
	145	+curl -X POST https://iam.ebrains.eu/auth/realms/hbp/clients-registrations/default/ \
111	111	-H "Authorization: Bearer ${clb_dev_token}" \
112	112	-H 'Content-Type: application/json' \
113	113	-d '{
...	...	@@ -195,7 +195,7 @@
195	195	clb_reg_token=...
196	196
197	197	# Update the client
198		-curl -X PUT https://iam.humanbrainproject.eu/auth/realms/hbp/clients-registrations/default/my-awesome-client \
	233	+curl -X PUT https://iam.ebrains.eu/auth/realms/hbp/clients-registrations/default/my-awesome-client \
199	199	-H "Authorization: Bearer ${clb_reg_token}" \
200	200	-H 'Content-Type: application/json' \
201	201	-d '{
...	...	@@ -214,7 +214,5 @@
214	214	Note that your need to provide your client id both in the endpoint URL and within the body of the request.
215	215
216	216	{{warning}}
217		-/!\ ** Each time you modify your client, a new registration access token will be generated. You need to track of your token changes to keep access to your client.   **/!\
	252	+/!\ ** Each time you modify your client, a new registration access token will be generated. You need to keep track of your token changes to keep access to your client.   **/!\
218	218	{{/warning}}
219		-
220		-== ==