Hi Neil,

This might not be your issue. But maybe it helps.

If your using SAML authentication. This can happen if the correct SAML login was used however IFS was unable to match it to an IFS User.

This results in an authenticated user with no permissions. If using SAML try enabling the default IDP for this user and testing that way. If it then works the problem is not permissions but linking the IFS user and SAML user.

Hi, @a.hutchings

thanks for your response but I’m still inclined to think that it is a Permissions problem as I have already tried the approach whereby I have granted all projections to a particular Permission Set and allocated that Permission Set to a particular user which is then able to log on with full application availability.

It seems that it is a problem with identifying the correct subset of projections that apply to a particular user. 

Cheers,

Neil.

Hi All,

I have added two base permission sets, FND_CONNECT and FND_WEBENDUSER_MAIN to the IFS user concerned and that has enabled me to log on to IFSCloud successfully.

So it seems that the answer was simply to add these two permission sets to the user.

Cheers,

Neil.

Hi @Neil Guild ,

After update do 22R1, I am having the exact same problem, and I tried your approaches but it didn’t work. I entered the permission set manually from Oracle Database.

Do you have any  others clues?

Hi,

I don’t know what state your 22R1 system is in or how you’ve handled the migration so far. We used IFS to migrate our APPS8 system to IFS Cloud and our APPS8 users formed the basis for the users in IFS Cloud. Although the structure of the users is very different between APPS8 and IFS Cloud, there are two base permission sets which are necessary for any user to log on in IFS Cloud and they were not present and that is why adding them enabled those users to logon.

Basically, the building blocks for a user are permission sets which have access to a set of screens (known as Projections in IFS Cloud). Users are then granted a Permission set which has access to a set of screens (Projections).

When we started off, we had a ‘Super user’ which had access to all screens and we used this one to identify the names of Projections that were necessary for each user type present in our original APPS8 system.

There is extensive documentation available onlineL-

Users - Technical Documentation For IFS Cloud

Cheers,

Neil.

Morning,

After many days of research and no answer from IFS, I found the problem. We need to add your application owner in prepare.sql file, like this:

DEFINE APPLICATION_OWNER = YOUR APPLICATION OWNER USER.

After that, everything runs without problems.

Thanks,

Gianni 

Hi @gianni.neves ,

You seem to be handling your migration in a different way to us.

Congratulations on finding the answer. I would not have been able to help you to discover that answer!

Cheers,

Neil.

No worries @Neil Guild,

I am tired to wait after IFS and I decide that if we want to progress on the upgrade, we need to go find the answers. It is much faster than waiting for IFS.

Let me know if you have questions, sometimes we can help.

Thanks,

Hi Gianni,

We got exactly the same case with your case. And not managed to get the solutions. We intended to try your solution. Just need to confirm some items below:

1. Does it mean, we need to rerun install.tem again?
2. But from our checking, install.tem did not call prepare.sql.
3. Or can we simply run the prepare.sql only, and then check if it solve the problems?

Regards,

Sutoto

Hi @sutoto ,

I don’t know which version of IFS cloud you are migration to. It has been one year already, so IFS and my knowledge advance a little bit, so, to answer your question:

1. Does it mean, we need to rerun install.tem again?
   1. You need to add you application owner in a files called DEFINE.TEM. You can find this file on “.\Deliveries\InstallationFiles\database”.
2. But from our checking, install.tem did not call prepare.sql.
   1. No, after change the DEFINE.TEM file, you need just to run the command below “.\installer.cmd --set action=install --values values.yaml”
3. Or can we simply run the prepare.sql only, and then check if it solve the problems?
   1. Like I told before, you can run just “.\installer.cmd --set action=install --values values.yaml” and everything must be deploy, either database objects and application tier.

We are already on 24R1.3, so below, you have IFS document explain the commands for 22R1.

Installer Actions - Technical Documentation For IFS Cloud

Let me know if you have any more questions.

Gianni Neves

Hi Gianni,

Thanks for your advice.

Hi All,

 

We are in the process of migrating from APPS8 to IFS Cloud and I’m having trouble updating a particular user profile so that I can use it to access IFS Cloud. I have chosen one of the simplest users (minimal screens/functions available) which requires minimal modifications.

I have allocated the appropriate, I think, Projections to a Permission set for this user but when I try to log on I get a number of popup windows with errors relating to Profile and Person info.

See below:-

 

Can anyone point me in the right direction to help resolve my difficulties with logging on to IFS Cloud please?

 

Cheers,

Neil.

 

Hi Neil,

Did you add the permission set via PL/SQL or via Application? We have similar case of error. But The error applied to all users, IFSADMIN also received the same error upon login. By then our admin user unable to grant permission sets for normal IFS users.

Regards,

Sutoto

Hi Neil,

My previous replay’s quote should be for this post. Not your post of the first discussion.

Thanks,

Sutoto