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.
We are using Custom Scheduler to create the Reportcaster schedule and it worked well with WF8105 but when we move the same code to WF8201, it throws "Invalid username and password" error on Logon script.
What are we missing here?
The userid and password we are using is letting us to get in to WF Client, Server, and also able to create the Reportcaster schedule.This message has been edited. Last edited by: WFDevConsultant,
Between 8105 and 8201, there been no change as far as sending credentials for the signOn action. But, there has been a change as far as the CSRF (Cross-Site Request Forgery) Token being returned in the response of the signOn action. This needs to be sent as one of the parameters of subsequent requests. eg. IBIWF_SES_AUTH_TOKEN=wwefojeweofjpppj
But, if you were not sending the CSRF token, you would receive a 403- Forbidden error.
Not invalid credentials.
Efrem
Posts: 229 | Location: New York | Registered: July 27, 2004