Here you can find the answers and help on common topics regarding DocuMasker multi-user and OEM licensing.
What is an OEM license?
An OEM license grants the licensee the right to use DocuMasker as part of their own product or software solution. An OEM licensee has entered into an agreement with R2B Software regarding the use of DocuMasker.
What is a Bearer token?
A bearer token is a code representing a licensee. If this code is passed in a request, ie passed to DocuMasker, the caller is granted access according to the related license. Bearer token is our current method of choice for separation between the customer, buying a DocuMasker license, and the end-users of that license.
I’ve got multiple users, do I need to handle the Bearer token?
No, you may register each individual end-user, by email address, instead. The bearer token is just an option. Consider using it if your userbase is large or somehow unknown. If you have received a bearer token to begin with, it is because your license is unlimited with regard to the user count. Typically, OEM licenses allows for an unlimited number of users.
What does Bearer token got to do with OEM?
OEM licenses pertaining to DocuMasker Software-as-a-Service includes using a bearer token to access the service. However, bearer tokens are also used in other multi-user scenarios, governed not by agreements (OEM) but rather by various usage quotas.
Is OEM and multi-user licensing the same thing?
No, there are multi-users licenses, including unlimited ones, available for direct purchase in our shop. This said, an OEM license is, generally, a multi-user license allowing the licensee to handle any number of users.
How can I make use of my bearer token?
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>