As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I have set up my environment to log users into their Dashboards via a Realm connector to Active Directory and all is working as it should. However, now I can no longer access MRE via Dev Studio. It asks for a username and password and does not provide access whether I provide the old credentials in MRE or my legit Active Directory credentials. Any suggestions on how to proceed? Not being able to develop code will make for some serious buzzkill on the project.
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
Did you change your Web Component Authentication in Developer Studio in the properties of the environment?
We don't use AD, but we do use SiteMinder so any protected environment we have to change that setting. We also have a custom dssso.xml file for our SiteMinder environment.
Not sure this is much help, but something else to look at.
As Matt told, we do use SITEMINDER/WebSEAL to authenticate. After selecting the appropriate component, click 'Settings', re-check your LOGON resource URL once and you might need to supply the Junction path as well. Also, increase the connection timeout to 200. It may help, not sure of it.
Thanks, Rifaz
-Rifaz
WebFOCUS 7.7.x and 8.x
Posts: 406 | Location: India | Registered: June 13, 2013
Thank you for the responses. I needed to change the settings on the Client url for Dev Studio.
Initially it was set to contact port 8080, Apache, but with consolidated login in the mix it needs to pass through IIS first, which means I need to contact port 80 instead. IIS on port 80 adds the Active Directory ID and forwards the request to port 8080. Once I changed the connection to 80 Consolidated Login magically woke up in Dev Studio.
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007