Lifetime: Admin Doesnt Have a Role

Hi Guys,

I recently installed the lifetime.oap in our dev environment. I am currently encountering below issue.

Basically what I did was:

1. Set-up the Platform Service. 

2. Login to Service Center for the first time and change the Password.

3. Upload the License.

4. Create Users and Assign Role to the developers

5. Install the lifetime oap that is located at the Outsystems Installed Directory.

6. Access the lifetime url "servername/lifetimesdk", and redirected to the login page

7. Input the admin credential of the service center and I am getting this error. I have check the service center and the lifetime is already publish and the service center admin user has full control of it.




Any inputs appreciated.

Thank you



Hello,

Take a look at this documentation. Also, take a look at this post.


Cheers!

Armando Gomes wrote:

Hello,

Take a look at this documentation. Also, take a look at this post.


Cheers!

Armando,

Right now are as a temporary solution we manually publish the code to the QQ/UAT Environment.

The project just started(license was bought September 2018) and I notice that the dev environment has unlimited AO and is about to expire in November while the QA/UAT Environment has 500AO Limit.

I think the dev environment license if I am not mistaken is a developer edition. Does it have something to do with this?

I also check the table mention in the thread the AUTH something table and currently it has no record at all since we never had the chance to login to lifetime(not even once) because of the issue.


Hi MIchael,


The project just started(license was bought September 2018) and I notice that the dev environment has unlimited AO and is about to expire in November while the QA/UAT Environment has 500AO Limit.

I think the dev environment license if I am not mistaken is a developer edition. Does it have something to do with this?

------> This is part of the license, they are providing you unlimited AO in dev but for QA/Prod you have 500AO limit.

OS license contains this features.


Thanks,

Rajat Agrawal

We had the same problem. We worked with OutSystems support, there was a bug in the Lifetime solution. I do not know how the fix will be distributed (as a separate Lifetime fix or as a new version of the Platform Server), but the fix is there.

Suggest you reach out to OutSystems support for assistance to get up and running.

J.Ja

Justin James wrote:

We had the same problem. We worked with OutSystems support, there was a bug in the Lifetime solution. I do not know how the fix will be distributed (as a separate Lifetime fix or as a new version of the Platform Server), but the fix is there.

Suggest you reach out to OutSystems support for assistance to get up and running.

J.Ja

Thank you for all your help guys. I will coordinate this issue with outsystems support.


Posting here the instruction that was provided to me by Support when I experienced this issue


since you are not being able to login to LifeTime with admin credentials (admin doesn't have a role), it seems like something didn't go as expected when bootstrapping LifeTime's users.


This bootstrap operation is performed by a timer of the LifeTimeEngine eSpace at publishing time, in order to try to overcome this issue please proceed as follows:

  1. Restart the Scheduler Service because after the restart it will pick all the missing timers and run them;
  2. Access Service Center and go to the LifeTimeEngine eSpace;
  3. Select the Timers tab;
  4. Left click on the Bootstrap-timer;
  5. Activate the timer by pressing the 'Activate' button;
  6. Run the timer by pressing the 'Run Now' button;
  7. Check the timer log for this Bootstrap-timer and see if it finished executing without any errors.

You may also need to run the GrantAlllRolesToAdmin Timer manually (Users eSpace).


John

Hi there.

Did your issue was fixed?

We installed the newest version and met the same question. It seems didn't be fixed.

We have performed the bootstrap operation and found that bootstrap is not working.

"Timer BootStrap error (inside action 'BootStrap'). Timer duration = 0 secs: The request failed with HTTP status 404: Not Found. [retry 3 of 3 scheduled]"

Tony