@MR10 Thats what I was worried about. Yes we already know which role needs what screens/functions, but to click this all together again is crazy time consuming
@MR10 We will shortly start the transition as well.What do you mean with “not having to set it up from scratch … saves a lot of time”? We have roughly 100 permission sets what would need to be retranslated to Aurena, and we just don’t see this being done manually.Any conversion ideas are highly valued.ThanksDominik
Dear allwe have occasionally had the same issue using browser or desktop shortcuts that launch directly the ifs.Fnd.Explorer.application https://xxxx.xxxxx.xxx/client/runtime/Ifs.Fnd.Explorer.application. Going through the normal web interface to launch IFS Enterprise Explorer fixed it, and any subsequent attempts through the link started to work again. best regardsDominik
Hi PeshalaPlease see attached screenshot:manually run the jobs gives much better parameters to define the periodsWe’d expect similar parameters when we schedule, using current open period
Hi PeshalaThis is how its set on our environment, setup in June, and it worked for the period of June, but now in July does nothng.
@Mark.Feldpausch Hi Mark, did you ever get any response to this. We appear to face the same issue with UPD5. Thanks, Dominik
We tried using new Database Tasks and select the export APIs. Unfortunately its not allowed to use those due to some character limitations.I could imagine custom code would have to be written and scheduled, but we do not have yet the skills/resources to accomplish this.
@WBRWILLIAM I gave up with Enterprise Explorer and Aurena, and have a working configuration now over Azure, which redirects me to my Cloud IDP. That is a step more, rather than directly to the Cloud IDP, but it appears to work. For Aurena B2B, I will most likely leverage the existing IDP configuration, but there I face the issue that IFS only reads from AD, and not LDAP, which would be useful to import suppliers/customer login accounts.
@WBRWILLIAM I have a working configuration for Aurena. Enterprise Explorer unfortunately not. After 30 minutes I receive the reauthentication error, indicating that something is wrong with the fresh tokens. Since we have just introduced MS O365 integrated with Okta as IDP, I will try this route now. IFS → Azure → Okta login route.
Hi Bruce We ran into issues during business hours when tables/views were locked and ended up with unsycnronized views causing issues for certain processes/prints. My IFS consultant recommend off hours for changes. Dominik
Hi Srikanth I would say Okta is fully compliant OIDC https://www.okta.com/openid-connect/ Identity Provider, minus the things Microsoft adds to make ADFS/Azure a bit more special (and less standard). Unfortunately there is no documentation out there what IFS requires, and its a long trial and error approach. Last missing piece is the refresh token for EE, which is not working at all and I don’t even see an attempt from IFS to get a new token. I’ll keep you updated. Thanks Dominik
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.