I installed a new pc

I installed a xampp

I copy/unzip all boa-framework to c:\xamp\htdocs

I don't modify a licence.json

Then I run http://localhost

It ask me a user (en), password ( en01 ) and APIurl ( empty by default )

and show me : 

Licence Invalid
You must purchase licence and added it on application

I know that I have done something wrong but I don't know where ...

Thanks in advance

Best Regards

Osvaldo Ramirez

Install XAMPP

Unzip boa.zip on c:\xampp\htdocs

Modify my licence.json to connect to my iAPI, 

( I didn't run the iAPI yet )

I Run http://localhost for first time, and the boa-framework ask me user and password, 

When I push the submit "LOG IN" the page show me 

Licence Invalid
You must purchase licence and added it on application

Maybe my licence is blocked ?

Best Regards

Osvaldo Ramirez

Are you telling that it works sometimes correct and sometimes not? 

Make sure to add the http://... in front of localhost.

Where is your BOA version installed? On a local server or is it available on the internet? In that case, can you send me the URL so I can check it? This way I can define if the problem is on the BOA server or in your iAPI.

Best regards,

Chris

I don't know How to describe my error; At the login page, some times, call the iAPI ( made with xb2net ) and some times show me a Licence Invalid and 

the URL show like this : localhost:82/auth/not-licence.

Then I close the FireFox, restart the webserve, restart the iAPI server, without success.

What Can I do ?

Best Regards

Osvaldo Ramirez

You can set an expiry time in your token. This way you can check for every request is the token is still valid. You can put extra information in your token, ex. User rights.

If the token isn’t valid anymore you can return an error to BOA. This will start the login screen.

oJon:error := “Token is expired” will give the user the login screen.

I’m using Chilkat active-x components to create a JWT (json web token), but you can create it as you wish.

This is some code to create the token.

oJwt := CreateObject("Chilkat_9_5_0.Jwt")

         oJose := CreateObject("Chilkat_9_5_0.JsonObject")

         oJose:AppendString("alg","HS256")

         oJose:AppendString("typ","JWT")

         oClaims := CreateObject("Chilkat_9_5_0.JsonObject")

         oClaims:AppendString("user",cUser)

         oClaims:AppendString("language",cTaal)    

         oClaims:AddIntAt(-1,"key",nCode)

         // '  Set the timestamp of when the JWT was created to now.

         nCurDateTime := oJwt:GenNumericDate(0)

         oClaims:AddIntAt(-1,"iat",nCurDateTime)

         //Set the "not process before" timestamp to now.

         oClaims:AddIntAt(-1,"nbf",nCurDateTime)

         //  Set the timestamp defining an expiration time (end time) for the token

         //  to be now + 2 hour (7200 seconds)

         oClaims:AddIntAt(-1,"exp",nCurDateTime + (3600*12) ) // 12 hours valid

         //  Produce the smallest possible JWT:

         oJwt:AutoCompact = 1

         cJwt := ojwt:CreateJwt(oJose:Emit(),oClaims:Emit(),cPassword)

I hope this gives you an answer to your question.

Best regards,

Chris

Regarding logout: As long as no logout is selected on the PC, the front end can be restarted even days later without a login being requested again.

I would like to prevent this and determine from the server when a user has to register again. For example: If user A simply closes the browser without selecting logout, user B can continue userA's session without logging in. I'm looking for a way to determine from the server that a user has to log in again. For example, all tokens should expire at 3:00 a.m. and force users to log in again.

• At login time there is one request to our licence server. This will check if you are working with a demo version, or if you have a personal licence key.
• The licence server will return the days left in case of a demo version.

There could arise a problem in case a version was used on an intranet without external internet acces, or in case our licence server didn't respond to the request. The use at the client side could not login, and the browser was waiting for a response.

With the new version BOA will proceed in the above cases. This way you will never be blocked because of technical issues of that kind.

Regards,

Chris

There was a question if BOA would work with Harbour.

The answer is yes, why not. As soon as you can setup a rest-API, you can use BOA. Since there is the hbhttpd for Harbour, to create your own web server, you have everything you need to start with BOA.

regards,

Chris.