I was able to adjust the Default Address Space to 10.0.0.0/16, and now have 10.0.0.0/24 - Where the Self Hosted BI Infrastructure exists10.0.255.0/27 - for the GatewayStill unclear on how I can use these details to fill the form for VPN Connection.
Hi @devin.amarasekara It means when have two AD users: “Jan.Kowalski@domain.com” and “Jan.Kowal@domain.com” SCIM synchronization will fail? HI @knepiosko, sorry for the really late reply. But I think yes. Since the Identity would be JANKOW for both.and @cedric pimont , yes that’s what I understood as well. And I hope there will be a workaround eventually as well for the Identity Generation.
Hi @Charith Epitawatta , Yea I downloaded the buildhome again and extracted it and still the solutionset.yaml was missing. Also I noticed that in the Customer Solution Repository and Customer Baseline Repository, there is only FNDBAS component. Is that normal for remote deployment buildplace? I checked in a cloud deployment buildplace and in that all the necessary components were present.Will this be resolved by recreating the buildhome as well?Thanks,Devin
I reached out to IFS through support channels and the solution suggested was that from 23R1 onwards there will be User Group Provisioning with Azure Active Directory on IFS Cloud. Therefore to set the Permission set to the User Group and to set the Users to that User Group. Will test it out when we get the 23R1 release.
I reached out through the support channels and it seems this is a limitation from the SCIM side.“Regarding the Identity creation, unfortunately there is no mechanism available to override the current identity creation process in SCIM provisioning. It is a limitation in the SCIM not in the IFS side. Also there is no SCIM attribute available to map the identity value as a custom option.”
Got a similar issue while doing a fresh installation because the linux directories and files of /home/ifs did not have the correct set of permissions. Had to correct the permissions as below. Not sure if this would help or not. Best Regards, Devin Hi Devin, Permissions are correct (ifs user have access). ifs@xxxxprod:/home$ ls -all total 12 drwxr-xr-x 3 root root 4096 Oct 4 2021 . drwxr-xr-x 21 root root 4096 Jan 5 10:38 .. drwxr-xr-x 5 ifs ifs 4096 Mar 17 14:09 ifs ifs@xxxxprod:~$ ls -all total 44 drwxr-xr-x 5 ifs ifs 4096 Mar 17 14:09 . drwxr-xr-x 3 root root 4096 Oct 4 2021 .. -rw------- 1 ifs ifs 442 Mar 17 14:08 .bash_history -rw-r--r-- 1 ifs ifs 220 Feb 25 2020 .bash_logout -rw-r--r-- 1 ifs ifs 3771 Feb 25 2020 .bashrc drwx------ 2 ifs ifs 4096 Oct 4 2021 .cache -rw-r--r-- 1 ifs ifs 807 Feb 25 2020 .profile drwx------ 3 ifs ifs 4096 Jan 5 10:44 snap drwxrwxr-x 2 ifs ifs 4096 Jan 5 10:37 .ssh ifs@xxxxprod:~$ cd .ssh/ ifs@xxxx
Got a similar issue while doing a fresh installation because the linux directories and files of /home/ifs did not have the correct set of permissions. Had to correct the permissions as below. Not sure if this would help or not. Best Regards,Devin
Again it seemed to be an IP issue, I have given the hostname instead of the host ip for the jdbc connection. This seemed to resolve the issue and the db-init executed.
Hi @Charith Epitawatta , I was able to solve the above issue. It was due to a IP address error when defining in /etc/hosts. I have resolved that issue. But now I am getting the following error. The firewalls are disabled in all the three VM’s. From my understanding the db-init pod is trying to fetch certificates but since it cant, its trying to extract a key from an empty string. Do you have any idea where the pod is trying to fetch the certificates from?
Hi @Shirantha Herath ,I had to change the generated private key on the windows management server to ReadOnly and had to remove all the other users except the admin user I was using.Afterwards I had to set proper permission for ‘ifs’ user in the middle tier vm. for the /home/ifs folder and its content. Had to enable PubkeyAuthentication in the sshd_config file in the middle tier as well. Since it was by default commented.Since this was done on a Ubuntu VM in Azure had to do some configurations previously, during which permission for the folders and files werent properly set or modified.
It was a permission issue on both windows side folders and keys, and as well as permission of the directories in linux and the files. Managed to solve by setting the right set of permissions.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
