Thank You
Hi @dominikdurrer Have You received any valuable output on You ticket? I am asking because we have customer on 23R2 release and SCIM configuration(Azure AD). The behaviour is very upredictible. One time user identity is ADAM967 next time ADAKAM for Adam Kaminsky. Once phone number is synchronized on the other time not. Azure privisioning logs show many errors event if we using only supported SCIM attributes follow the documentationIndex - Technical Documentation For IFS CloudWhen user is removed from AD group then on IFS side sometimes is not removed, etc. Last one problem is most important because we manage permissions through the user groups.I spent many hours but still do not understand it and predict behaviour. Is seems that provisioning on demand is a bit different than automatic provisioning.I need any kind of help to be closer with understanding this.
Hi @CRUNDELL Have You got an answer from You ticket?I had following answer from end: This option is not available in public IFS Cloud Documentation. To make use of this IFS Cloud and B2B please browse to this section from within the product documentation inside IFS Cloud. Hence this is not an issue, it's the behavior of cloud documentation in Docs.ifs.com.
Hi In IFS Cloud You need to open Debug console. There are tabs Page Info and Server Invoke where You can find views linked to each tab and queries sent to the database as well.
I have tested provisioning with one of our customer on 23R2 and one time user “Agata Kowalska” was created with identity AGAKOW second time AGATA1. If someone wants to check logic look inside package: SCIM_HANDLING_SVC and procedure Create_User___ to understand behaviour.
Hi @CParkinson Check these steps:**Increasing .NET Access Provider timeout in IFS Touch Apps Server**1. Navigate to the TAS installation folder (Default is C:\inetpub\IFS Touch Apps Server)2. Open the Web.config file in a text editor3. Find the line for the .NET AP timeout<add key="AccessProviderConnectionTimeout" value="00:00:00" />1. Set the value to 90 seconds (1.5 minutes)<add key="AccessProviderConnectionTimeout" value="00:01:30" />1.Save the file2.Restart IIS
Hi @Shaaz You have just confirmed bug in application. Is it mean it will be patched?
Hi @Mike.Hollifield I reported problem with creation Person through the SCIM synchronizatiion on one of my ticket. I have received message that it will be considered in 24R2.
In my opinion format is not a problem. Are You sure that Print Agent has been installed and works correctly?
Hi @VanChampS But I think if You find some gaps in predefined LTU permission set You might report it as a standard bug.
Already have an account? Login
No account yet? Create an account
Enter your username or 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.