Last Modified October 1, 2026
- Home
- Guides
- Activation API V1
- SAAS App Demo
A typical SAAS application, as demonstrated by our SAAS App Code Sample, would require:
- an initial Account Activation (i.e. registration) to activate the License for the browser
- thereafter, a Login with password every time a new browser session is started (or has expired)
The following would be required in your Web App:
Your main Landing page (can be the Login or Account Activation page) would perform a
validation of the Web License,
and redirect to the Login or Account Activation page
in the Login Page
- the typical "UserID / Password " inputs are required. You can implement either of:
- License Code as the "UserID"
- License Email as the "UserID"
- the page could include
- DeActivate button
- Resend Password button
an Account Activation page where the User would
activate the browser on their
for your SAAS Application:
on the initial activation of the License, this would set the License Password
and the License Email
on subsequent activations, this would re-activate the browser on the License
The page could include:
the SAAS App itself
A live SAAS App demo using the Activation API V1 can be accessed here:
SAAS Activation Demo
You can get a License Code for our HelloWorld P0002964 demo product
on our Resources -> Code Samples page.
SAAS Demo explained
The Demo is a straightforward implementation of the software_DNA protection requiring only a few Activation API calls which interact with the DNA
Servers using HTTPS POST Requests and JSON encoded parameters, and includes two web pages:
- a combined Landing / Login / Account Activation page
- the SAAS App page
The User would have purchased a License or Subscription to your SAAS Application via your store-front and received his License Activation
Code.
Below are screen shots from our live SAAS Web Activation Demo that you can access here:
SAAS Activation Demo
You can get a License Code for our HelloWorld P0002964 demo product
on our Resources -> Code Samples page.
SAAS App Flow
Both the Custom and StreamLined activation methods are supported by the Activation API and summarized here.
In the LANDING page
- On page load, validate the DNA License if one exists:
- use
DNASetProperties to assign settings used by Helper Functions
, ex: licenseCookieName
- perform a
WEB_Validate which includes a Local Validation, and
if required, a DNA Server Validation
- Redirect to the Login page if successful, or the Account Activation page if not
The Landing page can be combined with the Login or Account Activation page
In the LOGIN page
- capture the UserID and the
License Password from the User
(The UserID is either the License Code or the License Email depending on your implementation)
- perform a
WEB_Reactivate
- if valid, then continue to the SAAS application web pages
- if not valid, display an error message, and direct the User to the
Account Activation page
In the Account Activation page
Custom Activation
- get a License Activation Code from the User and perform a
WEB_Query
- based on the result, capture additional information which can include a License Password (*), a
NEW and NEVER Used Password (**), and License Email
- perform a
WEB_Activate_SAAS or WEB_Reactivate
- if valid, then continue to the SAAS application web pages
- if not valid, display an error message
|
StreamLined Activation
- get a License Activation Code, License Password(*) and
Email from the User
- perform a
WEB_Activate_SAAS
- if valid, then continue to the SAAS application web pages
- if not valid, display an error message
|
(*) Not required if User Authentication is not used
(**) Not required if Roll-Over Re-activation is not used