So far I have managed to solve my problems, but now I have a problem that is on both my test VM and in the AWS server that has been built.
It appears on both systems, if I create a new admin (access provider), I can not login unless I enable the realm permissions on the new user. Once I login, it appears that the new admin can not modify Profiles or Perminant Users.
On the VM, I can see in the rights, the default group right does not have the "YES" on each permssion.
I have enabled the debug log and I have attached a clean output.
I have installed this with php7.2 and cake 2.10.x the latest version, it must be something to do with the versions. I hope someone can look to try and figure out what is wrong otherwise it is back to DalorRadius!
The output errors only ocoure on clicking Profile or Users, this must be the reason the edit boxes are not being displayed.
Well it is official, I have gone through the install process using Ubuntu 16 and Cakephp 2.9.9 and creating a access provider is still broken.
Clearly this is an issue that exists in the current release and following the wikki guide using Ubuntu will give you a working system as long as you are not wanting to allow access providers or creating other admins to manage the system.
I have installed this to the tee and have been compiling applications from scratch since the late 90's, so this is not a nooby error.
The system funtcions well and the only way I can provide other users to use the system at a normal level is to bump them to super admin like root in the backend.
Not ideal. But if you have just installed it, try it out, create a new admin user and you will find you can not manage user or profiles due to errors above. real pitty....
If you are happy to use root between users or using the VM which does function correctly, how ever, we are trying to deploy this in aws so the VM is not an option.
I have also performed the install on a local VM which is displaying exactly the same problems.
Wish the devs could look in to thism guess its back to crappy Dalor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
So far I have managed to solve my problems, but now I have a problem that is on both my test VM and in the AWS server that has been built.
It appears on both systems, if I create a new admin (access provider), I can not login unless I enable the realm permissions on the new user. Once I login, it appears that the new admin can not modify Profiles or Perminant Users.
On the VM, I can see in the rights, the default group right does not have the "YES" on each permssion.
I have enabled the debug log and I have attached a clean output.
I have installed this with php7.2 and cake 2.10.x the latest version, it must be something to do with the versions. I hope someone can look to try and figure out what is wrong otherwise it is back to DalorRadius!
The output errors only ocoure on clicking Profile or Users, this must be the reason the edit boxes are not being displayed.
Please help!
Paul
Well it is official, I have gone through the install process using Ubuntu 16 and Cakephp 2.9.9 and creating a access provider is still broken.
Clearly this is an issue that exists in the current release and following the wikki guide using Ubuntu will give you a working system as long as you are not wanting to allow access providers or creating other admins to manage the system.
I have installed this to the tee and have been compiling applications from scratch since the late 90's, so this is not a nooby error.
The system funtcions well and the only way I can provide other users to use the system at a normal level is to bump them to super admin like root in the backend.
Not ideal. But if you have just installed it, try it out, create a new admin user and you will find you can not manage user or profiles due to errors above. real pitty....
If you are happy to use root between users or using the VM which does function correctly, how ever, we are trying to deploy this in aws so the VM is not an option.
I have also performed the install on a local VM which is displaying exactly the same problems.
Wish the devs could look in to thism guess its back to crappy Dalor
Hi friend How did you create the user in the backend can you help me