Hi.This is planned for 24R2. /Subhashini
Hi,I’m afraid, this is an huge implementation, so definitely this will not go for a Service Update. This will be planned for a future Release soon. ( most probably for 24R2) /Subhashini
Hi, Yes. Currently it’s not possible to configure the timeouts for IFS Cloud. It is set in Keycloak. We are trying to make it configurable from solution manager for 23R2 . /Subhashini I’m afraid, due to technical limitations we will not be able to deliver the possibility to change the session timeouts in 23R2. From the investigation we did, changing the values for the timeouts from keycloak admin console will make the environment unstable. So please don’t change the default values set by IFS. Current default values for session timeouts- Session Idle timeout - 2 hours Max session timeout - 10 hours. When will this be released again? - Still we are discussing when to release this fix. /Subhashini
Thanks for the input. We will consider this in a future release. /Subhashini
Hi, Its better to raise a ticket for this. So that this can be properly investigated. /Subhashini
Hi, May I know the version please?/Subhashini
I’m afraid, this is a risky change to do. So please wait till 23R2. /Subhashini
Hi, NO! don’t do it for Aurena. It should be only for what ever the IAM client used by MWO or for whole realm. We have never tested this for separate IAM Clients. From authentication side, we can only say, theoretically, it is possible to increase the timeout. But this needs to be validated from the relevant client side that they support it. Further there are dependencies between all these timeouts. you have to be very careful on those as well. @kathlk @JOOLSE I think you should test this and confirm from MWO side. If the customer decided to increase the timeouts for whole application we can help. /Subhashini
Hi @Technical Toby , Why do you want to create a user without a person from SCIM? Using SCIM we sync the users in your AD. Aren’t they real persons/employees? Could you please explain us along with a valid example? /Subhashini
Hi, Could you please check the ifsapp-iam container log for any errors? As I see, this could be due to either incorrect configuration or certificate issue. /Subhashini
HI, It is possible to set the timeout from keycloak. But it will not persist. With the next delivery it will reset to default. /Subhashini
Hi, Yes. Currently it’s not possible to configure the timeouts for IFS Cloud. It is set in Keycloak. We are trying to make it configurable from solution manager for 23R2 . /Subhashini
@Malin Norgren How did you managed to do it manually?
@hamalk as guided by your team this image was pushed. https://ifsdev.atlassian.net/browse/EPZET-13431 /Subs
Authentication is totally different from APPS 10 to IFS Cloud Application. ( Latest release. Not APPS 10 hosted in Cloud) so we can’t down port a solution from IFS Cloud to APPS 10 directly. If this is needed for APPS 10, that it new feature implementation and that needed to be prioritized properly through SVP or Product Managers. Customization for APPS 10 - I don't think its a good solution. Apps 10 Authorization goes through MWS.
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.
