Last modified by bougault on 2022/03/02 11:58

From version 12.1
edited by allan
on 2019/11/26 17:07
Change comment: There is no comment for this version
To version 10.1
edited by allan
on 2019/11/26 16:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -15,6 +15,7 @@
15 15  Only SGA2 accredited users will be automatically granted the developer accreditation.
16 16  )))
17 17  
18 +(% class="wikigeneratedid" %)
18 18  == Making your app available to users ==
19 19  
20 20  In order for you application to be installable by users, it needs to be registered within the [[Community Apps Catalogue>>doc:Apps.WebHome]].
... ... @@ -47,15 +47,6 @@
47 47  
48 48  You should now see how your app looks like within a collab.
49 49  
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 59  == Creating your OpenID Connect client ==
60 60  
61 61  The steps to create an OpenID Connect client are the following:
... ... @@ -225,4 +225,4 @@
225 225  /!\ ** 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.   **/!\
226 226  {{/warning}}
227 227  
228 -== ==
220 +== ==