Attempting to set up an instance of the Bluemix SSO service for use in an app. I created a service instance but when I click on the tile to open it so that I can configure the settings I get:
com.ibm.sec.iam.platform.ui.DashboardException: CTJSO1501E You have arrived at this page without valid parameters. You must visit this page via the Bluemix administration console.
Now, I thought I was in the Bluemix administration console. I mean, I'm coming from this page:
https://new-console.ng.bluemix.net/dashboard/all
I tried coming at this from other paths but every time I try to open the service I get this error.
Would appreciate any thoughts on what is wrong here or how I might workaround this failure.
Mike
I am not seeing this problem. Which browser do you use? You can try switching to a different browser, or cleaning current browser cache to see if that helps.
I get the same when using Safari on Mac. Using Chrome, it goes through.
Related
I have added community applications to our Dashboard by clicking on Add Apps(home page), and assigned to the people. its working fine, people able to access Community Software, but whenever we are intended to create our custom app(Jive demo sandbox) from admin panel and assigned people its not working as expected. even the admin not able to access the app it is showing message "Sorry, you can't access Jive Software because you are not assigned this app in Okta".
i have followed the integration process from
http://developer.okta.com/use_cases/integrate_with_okta/
please help me that i am missing any integrations or configurations
There is not sufficient information in this question to be able to answer. Have you tried reaching out to Okta Support? They should be able to check your configuration with your permission and help you with it.
I have tested and used Bluemix SSO with a Liberty runtime on Bluemix successfully with the G+ login provider. Now I added LinkedIn and Cloud Directory providers as well.
However, when I try to login, it still always redirects me to the G+ login. When I disable G+ in the SSO service, it tells me "FBTIAS030E No login methods are configured.", even though the other two are enabled in the SSO config (and verified in case of LinkedIn).
I have restarted the runtime, and even re-staged it, to no avail.
Any ideas?
Did you customize the login.html page? If you did, you can get the default template back by using the reset button at the Custom Design page. The default template displays the list of Identity Providers that you set up.
Sorry for the late reply, but I found the problem. The nice big switches in front of each provider (in the dashboard for the SSO service) were doing nothing in terms of switching providers on or off. You need to go to the "integrate" tab where the real switches are to enable the other providers.
all:
We have a software developer building a web site with Facebook login for our company. They have told us to register a Facebook application.
For the moment, the beta application is hosted in a development environment. I would like to start testing also the Facebook integration. But when I access to the application page in Facebook, I get an error.
I think it might be related to an attribute I find in the first page of the app configuration. The attribute is called "Hosting URL".
The option seems to be linked to some kind of hosting service provided by Heroku. I don't know exactly what is that, but I would say we do not need it. We will use our own hosting server and, what's more, our application is developed in a language different that the one Heroku supports.
Could somebody confirm us which is the problem and, if it is possible, give us a hint to solve it?
Thank a lot in advance,
-The SportPoket team
The "Hosting URL" is meant to be the public web address of your finished production application. During development however, you only need to provide the URL for the app that is accessible from your web browser. If you are running a local web server on port 5000, http://127.0.0.1:5000/ will work.
Heroku is just one of the suggested hosting services for Facebook and you don't have to use it, but the documentation can be helpful. More about setting up a Facebook app dev env can be found here: https://devcenter.heroku.com/articles/facebook#1-creating-a-development-facebook-app
Infinite Reload With Rotating State Param in my facebook web app, this problem occur suddenly and suddenly all fb app on my server stop working
Page is refreshing again and again and not able to open ,
script work fine in other serverbut fails to work in this , is there any server config to handle facebook app.
You can chk issue at Link - gomandi.com/visit/
State Token is Refreshing again and again in all website hosted in my server , Looks like some Server confiG. issue is there . Can anyone help me with this.as i am my server support team unable to find this issue why my server fails to connect with fb server or viceversa.
SAME APP WORK IN OTHER SERVER !!
Based upon the comments on the question above, what you need to do is to create a brand new app for the different domain names. So you can have specific URLs for each domain specified in each of the app's app settings. So if there are three domains, then I'd recommend three apps configured correctly to point to each of those three domains.
So, for whatever reason, some people can't see the custom facebook page tab. Not sure why, especially when I can see it just fine.
Link: http://on.fb.me/rKNxUS
Let me know if you need more info.
Do you have a https version of the page tab? If they're account always uses ssl and you don't you might run into issues. Other times I've seen resetting the app secret help with issues like this.
It shows a standard browser error page to me. "This webpage is not available Google Chrome's connection attempt to incontrolwebsites.com was rejected. The website may be down, or your network may not be properly configured."
May it be possible you didn't upload the webpage to the production server?
If it opens correctly from your machine: check that you don't have a custom DNS setting to point to your local webserver instead of the production server.