# HG changeset patch
# User amazy
# Date 1567505091 -7200
# Node ID c310a795c1335c69aae84060935963722eb1163d
# Parent  869d6efbb54cb2c01d072fd1e8c7484c2926e7f4
auth-token in search params

diff -r 869d6efbb54c -r c310a795c133 Sphinx/source/faq/authentication.rst
--- a/Sphinx/source/faq/authentication.rst	Mon Sep 02 10:04:57 2019 +0200
+++ b/Sphinx/source/faq/authentication.rst	Tue Sep 03 12:04:51 2019 +0200
@@ -43,3 +43,5 @@
 * Create a :ref:`new Web user interface <improving-interface>` on the
   top of the REST API of Orthanc, using your favorite framework
   (Meteor, AngularJS, Ember.js, Node.js...).
+* Pass an :ref:`authorization token <orthanc-explorer-authorization>` 
+  in the url search params when opening the Orthanc Explorer.
diff -r 869d6efbb54c -r c310a795c133 Sphinx/source/plugins/authorization.rst
--- a/Sphinx/source/plugins/authorization.rst	Mon Sep 02 10:04:57 2019 +0200
+++ b/Sphinx/source/plugins/authorization.rst	Tue Sep 03 12:04:51 2019 +0200
@@ -310,4 +310,23 @@
   service. Think for instance about an authorization mechanism that
   simply associates its studies to a set of granted users: In this case,
   the series and instance levels can be ignored.
-     
+
+
+.. _orthanc-explorer-authorization:
+
+Integration with the Orthanc Explorer
+-------------------------------------
+
+Starting from Orthanc 1.5.8, you can pass authorization tokens in the url
+search params when opening the Orthanc explorer i.e. 
+http://localhost:8042/app/explorer.html?token=1234.  This token will be 
+included as an HTTP header in every request sent to the Orthanc Rest API.  
+It will also be included in the url search params when opening the Orthanc 
+or Osimis viewer.  
+
+Only 3 tokens name will be recognized and forwarded: ``token``, ``auth-token``
+and ``authorization``.
+
+Please note that the Orthanc Explorer has not been designed to handle
+the authorization so, when an authorization is not granted, it will simply 
+display an empty page or an error message.