What's really odd is that when you export a workbook, you have the option to "not include Connection information" but then you do the import and it's clearly being included regardless of what you pick on that screen. @Bret Grinslade - Oracle Analytics-Oracle Any updates or comments on this behavior?

I know this an old item, but what if you have a semantic model in Dev and you want to promote to a higher environment? It seems like then your connection information would potentially break as well? Haven't tried the semantic modeler yet to see if this is the case. But the overwriting the connection when importing…

Has anyone come up with any workarounds for these issues?

I was able to add the group using the WLST commands @Gianni Ceresa provided. That will probably need to be the fix while we start to think about a possible alternative for our group management. Thanks!

Thanks yes, going to get the WLST going, try the command, and see what happens. I haven't had to spend very much time if any in the WLST so this be a slight lift for me. Need to finish that Weblogic training ;)

@SteveF-Oracle Am not able to add groups to roles in OAS2022 Console either, but am able to do so in EM

@Gianni Ceresa I guess the big question I'm seeing here… Do I have run that for every single role we have, or is there a global setting to set the force validation to be false rather than true?

@SteveF-Oracle From what I can see, in the console, if I go to an Application Role, and try to add a group, I see only a handful of groups, from the OAS System, and possibly from Active Directory, I'm presuming. The groups defined in our BISQLProvider don't show up there and you can't do any kind of a manual override. I'm…

Yes, support is saying not to apply this patch.

@BrandonH Is this for OAS 2025?

I filed a service request with support (SR 3-40773138741). They're basically telling me that this is THE behavior now in OAS. Our users are not going to be thrilled with this. I mean, if anything, I feel like it should use the same logout URL that is used when you click "Logout" from your user profile in the upper right…

It's a custom SSO proxy, written by one of our engineers. That's as much detail as I know about it. Am currently on vacation, so can seek out more information when I return next week.

Confirmed bi-environment.xml file is identical between OAS 2022 and OAS2025. Will probably go ahead and submit an SR with Oracle Support. Thanks.

Yea, I have that configured already. It works correctly when you explicitly log out. However, on a TIME OUT, the behavior is not the same as it was in our previous version of OAS (6.4) I'll take a look at that xml file, but I kind of feel like we uncovered another bug. Regards, Chad

Thank you, @Sumanth V -Oracle !

From Oracle Support: Due to a requirement from FMW, it was required to add a new administration port value to manager server. This had changed the order of ports to increment by 1. OAS documentation will be updated accordingly in the change of default port numbers.

FYI, I submitted this to support and they created the following bug for the Dev Team: bug 37840145 That link doesn't net anything, but just wanted to pass the info along.

Also, just noticed all of those ports shifted by up 1. I will have to look into my proxy to see if any of those ports are being specified.

Sounds good. Going to confirm some things on my end, put in a ticket request to update the firewall rules, then submit the SR/bug with Oracle. Great job Gianni!

Yes, we are installed on Linux RHEL9. [root@<OAS2022> ~]# netstat -anp | grep 951 tcp 0 0 <hostip>:47016 <hostip>:9511 ESTABLISHED 9719/sawserver tcp 0 0 <hostip>:58048 <hostip>:9512 ESTABLISHED 9431/nqsclustercont tcp 0 0 <hostip>:58170 <hostip>:9510 ESTABLISHED 9719/sawserver tcp 0 0 <hostip>:44488 <hostip>:9514…