I have keyrock of fiware in my own laptop though docker.
When I do in my browser htp://localhost:8000 , this link redirect to a login website, so it's okay.
When I put htp://localhost:8000/sign_up this link redirect to a register website, so it's okay also.
But then thing is, If I want to do that though GET and POST, how can I do?
I installed Postman in my laptop but, when I put GET http://localhost:8000 everything is okay.
But when I put GET htp://localhost:8000/v3/users if I want list users, doesn't work.
the last I readed in this page : https://developer.openstack.org/api-ref/identity/v3/#users
Could you help me, please?
Thank you very much,
Best Regards.
As stated in the link you put in your question:
"A user with no assigned roles has no access to OpenStack resources."
The right port for your request is 5000 (keystone) instead of 8000 (horizon): http://localhost:5000/v3/users
So, to do what you want, you have to assign some specific role to the user you are using to access the list of users and, besides, I think you have to pass a valid token (X-Auth-Token header) in the request headers.
I hope it can help you.
I gave you a reply here that I think is a more detailed version of the same question. I hope this helps you. Otherwise, we can follow it in that question.
Best regards
Related
When the user clicked on the logout button after successful logout user redirects back to callbackurl with additional query parameters.
You can see below the URL return
https://localhost:9443/?sp={spname}&tenantDomain=carbon.super
Can anyone please help me with how we can remove these two sp and tenantDomain parameters?
I found the below article, also there are these two additional parameters.
https://piraveenaparalogarajah.medium.com/rp-initiated-logout-with-wso2-identity-server-b1fde28c4d80
Can search the below text in the article for reference.
Redirect to post_logout_redirect_uri
This seems to be introduced with the fix done for https://github.com/wso2/product-is/issues/3266. It has added the service provider name and tenant domain as query parameters for the success flow as well in addition to the failure flows.
Unfortunately, there is no way to configure this. But you may report this at https://github.com/wso2/product-is/issues and the team will decide whether this needs to be fixed.
This issue is reported for IS 5.10.0:https://github.com/wso2/product-is/issues/12723
Originally posted as a reply to: Error: The requested URL "[no URL]", is invalid
I get this error but only with one specific website (which is my own). This must be linked to the website as it is happening on 3 different machines on 3 different networks (personal comp on personal wifi, phone on 4/3g and work pc on work network) and no other sites. Also, it happens no matter what you put after the domain name, weather its a real page or just '/sdjhlgajhsdfg'.
A reply to the other post said that it looks like somthing to do with akamai. As this is my site, i went to the CPanel and disabled the akamai options (over 24 hours ago). i do not need any kind of caching like this as it is a simple html css site with only a hand full of mostly text pages. The most complicated thing on the site is a downloadable pdf which i have actually just taken down.
The error ref number changes every time you refresh the page.
Reference #9.d7c33b8.1478565760.55ccef1
Reference #9.d7c33b8.1478566986.560a7c3
Reference #9.d7c33b8.1478567000.560b460
Any advice would be very much appreciated.
I finally found some time to contact my webserver provider.
I can see that the domain has been removed from the Akamai server.
However, the CNAME which was pointing to Akamai server was causing the
issue. I have removed the CNAME record.
after about half an hour its back up. theres some display issues with the layout, but at lease its displaying the relevant content and not the error.
When you see Invalid URL error, this indicates that the hostname (domain) is not recognized by the Akamai's network (production or staging).
More info at: https://control.akamai.com/search/kb/11327
Hope this helps.
If there is a reverse proxy in before akamai you may get this error.
Client > Reverse Proxy > Akamai > Your API, will give this error.
Let your reverse proxy strip "Host" header and sent by "Client" and try again.
That worked for me in a setup like this:
Browser > Caddy Server > Akamai > My API
in akamai i had to add a new property manager entry for the new url/cert then activate it in prod.
According to the OpenShift docs, the following should return a result:
curl -X GET https://openshift.redhat.com/broker/rest/api
However, any call to the API actually just returns a single whitespace - including those called with username & password.
I've confirmed the issue from several different machines accross the globe.
What might be the reason?
Inspired by a similar question regarding Twitter, I added .json at the end of the URL and it worked:
curl -X GET https://openshift.redhat.com/broker/rest/api.json
It's kind of disappointing that RedHat never replied to any inquiry regarding this issue.
The issue is logged here: https://bugzilla.redhat.com/show_bug.cgi?id=1324208
You can add yourself to the "cc" if you would like to be notified as the fix gets rolled out to production.
FYI, asking for help on a public forum and giving it only 4 hours for a response from the company seems a bit much. In the future it may be worth it for you to either check for open bugs, or to ask the company directly instead.
I set the authentication in control panel as below:
and i call the viewer by this code:
$.ajax({url: 'http://192.168.17.31/viewer',
headers: {'thisistheheadername':'thisistheheadername'},
type : 'GET'
});
but still request redirects to login page:
http://192.168.17.31/viewer/login
I'm not totally sure what you're trying to do. I've never seen AJAX used with Datazen like this, although I suppose I can understand how it might work. Of course, it won't be secure, because the browser could always indicate who the user should be--there's no checking.
The top chart in this answer might help you. But beyond that, what tells you it's sending to the login page? Where are you trying to display the results?
The two things I would check on outside of those, though, are:
Your header is not correct, unless you've got a user named "thisistheheadername" as well. You should be passing a username through that value. I don't recall specifically, but it could send you to the login page if it doesn't recognize the username.
Are you sure external authentication is enabled? I would check in the "Configuration" section on the server to ensure it isn't still "default." The core service must be stopped before changes are persisted.
Has anyone tried accessing bungie.net reach stats api (statistics from Halo Matchmaking)?
As described here http://www.bungie.net/fanclub/statsapi/Group/Resources/Article.aspx?cid=545064
I can't seem to get any data returned, for example if i use this (with correct API key and gamertag values of course) ignore the first 2 asterisks ...
**http://www.bungie.net/api/reach/reachapijson.svc/player/details/byplaylist/MyIdentifierAPIkey/Gamertag
I don't receive a response - but no errors either, am i doing something wrong?
looking to use this for a Titanium (appcelerator) app eventually.
Any help or advice welcome, thanks in advance.
Unfortunately the API is not yet live to the public. I asked in a Private Message. They didn't say when it would be live.
In the Docs that Achronos posted, he put spaces in the URL's, I'm not sure if those are supposed to be there or not, so I tried it with the spaces and I got a 403 Forbidden error page. When I remove all the spaces, I get an error page that says:
Request Error
The server encountered an error processing the request. See server logs for more details.
I kinda can't check the server logs though... Bungie did say they were having some issues with the site though, so this might be a biproduct of that. I want them to get it working soon though, I wanna see just what it can do!