The bearer token must be embedded in the Authorization HTTP header of each request to DocuMasker, according to “Authorization: Bearer your-token”. How to best accomplish this depends on your programming languange and/or software platform. If the bearer token simply represents a multi-user license and there is no actual integration needed, you may use the token in a reverse proxy setup. Below are reverse proxy settings for the Apache and IIS web servers. These settings allow a user, without personal license, to access DocuMasker on your behalf using url https://documasker.yourdomain.com.
In the Apache web server, add configuration similar to this:
<VirtualHost *:443>
ServerName documasker.yourdomain.com
SSLProxyEngine on
ProxyPass / https://documasker.oais.se/
ProxyPassReverse / https://documasker.oais.se/
RequestHeader set Authorization “Bearer your-token-goes-here”
</VirtualHost>
In the Microsoft IIS, provided the Application Request Routing (ARR) module is installed, create a web site and add configuration similar to this:
<rewrite>
<rules>
<rule name=”run via documasker.oais.se”>
<match url=”.*” />
<action type=”Rewrite” url=”https://documasker.oais.se/” />
<serverVariables>
<set name=”HTTP_AUTHORIZATION” value=”Bearer your-token-goes-here” />
</serverVariables>
</rule>
</rules>
</rewrite>