How do I pass the identity of the logged on user in an a webapplication to a service beeing called by the webserver?
My idea her is to set som kind of EndpointIdentity on the cahnnel. In my case this will be an GUID identifing the user's session on the webserver.
Anyone got any exprience on this.. Maybe I have misunderstood the concept?
Any idea's or links would be apriciated.
I have replied to one of the questions on Stackoverflow for a similar kind of problem:here
Please check, it will be helpful for your problem also.
Related
There is an option to persist messages on send on both RTMClient.sendMessageToPeer() and RTMChannel.sendMessage() methods via the SendMessagesOptions interface (which is the optional second parameter on both methods).
However I cannot find information on how and in what form these messages are persisted, and ultimately on how to retrieve the messages history.
Can someone point me in the right direction please? Thank you.
Apparently the feature is still in beta.
This answer is from their official repo at GitHub.
I confirmed with my colleagues, it's shown there but still in beta phase. if you believe you need this feature maybe you can try contacting sales person.
I have created a atlassin account for testing the Jira rest api and created a project and tickets under it.
I am able to access the projects but not the issues under it. Please find below for more info
Could someone please help me what permissions I am missing
We can access the issues using URL request for api as below
"https://site.atlassian.net/rest/api/2/search?jql=updated>-90d&startAt="
Not a permission issue, but you missed adding issueIdOrKey path parameter. JIRA attempts to identify the issue by the issueIdOrKey path parameter. This can be an issue id, or an issue key.
To get the issue details, you can use the following Jira Rest endpoint,
GET /rest/api/2/issue/{issueIdOrKey}
For your case it will be,
GET /rest/api/2/issue/BI-1
Frustrating issue with attempting to use REST to login to the BIM 360 Field API, it was suggested that to use the postman application in order to ensure that my code wasn't an issue, however I'm now getting an unauthorized error, this has been attempted with an admin account and a developer account with the same response (login details are definitely valid), I was wandering if anyone has encountered this problem before or has any idea how would go about getting past this, I need to get the ticket response in order to go any further with developing an application for this, I'm already in contact with someone from Autodesk but due to timezone differences responses are difficult!
I've attached a picture to highlight the simplicity of what I'm attempting to do with no joy!
Thanks in advance
Dan
In case somebody else hits the same issue, FYI -
Dan and I looked at this issue, and we learned (in a hard way) that the base URL for BIM 360 Field in European region is:
https://bim360field.eu.autodesk.com
Notice "eu" in the URL. In the U.S., it is https://bim360field.autodesk.com
I wrote a post about this, too, for future reference:
https://fieldofviewblog.wordpress.com/2016/08/18/base-url-for-bim-360-field-in-european-countries/
I also found it worked when I used https but not http although the examples in the help use http.
for a customer website I use Sabredav within a Typo3 Extension (webdav, by Kay Strobach). This
extension, "activates" sabredav when a user enters the following URL:
http://mycustomersite.com/index.php/dav
I can connect with GoodSync with no problems, everything works fine.
Now, I should go a step further. The address
data.mycustomersite.com
should "point" to the address above. Simple redirect seems not to
work, since I get errors.
I know, that this can be solved by mod_rewrite. Unfortunately I have
only a little knowledge of apache...
What exactly should I have to write in order to achieve this? And
where?
Thank you very much in advance.
Davide
You should write to an official typo3 mailing list, where e.g. Kay is reading and answering ;-)
I first encountered the concept of lazy registration the Ajax Patterns site, where they define it as accumulating "bits of information about the user as they interact, with formal registration occurring later on." I'm looking at doing something similar for my website, but I'd like to know a little bit more about best practices before I start implementing it. My site is about web development, but general best practices are great too. How have you implemented lazy registration on your sites or projects? Where have you seen it in the wild? What do you like or dislike about it?
Have a look at this vid, a very good overview of the lazy registration pattern:
http://www.90percentofeverything.com/2009/03/16/signup-forms-must-die-heres-how-we-killed-ours/
I say this not as a person who has designed such a site before, but as a person that might visit that site. :)
With that said, the thing that I would be the most concerned about is knowing what kind of information is being collected about me. And I think that there should be an option to opt out of collecting the information and instead entering it all during formal registration.
But other than that, if it makes registering for a website easier, I'd be all for it. I leave 9 out of 10 sites that require me to register to do stuff.
One way that I was thinking about implementing this is when users leave blog comments. A common Wordpress format is to allow site visitors to comment as long as they leave a name and an email address. If I followed a similar pattern and then after they submit their comment, ask them if they would also like to register by having username and password inputs right there, with their email pre-filled in the email address input. There would also be a message saying that if they choose not to register at that time, their email address won't be saved (other than in association with the blog comment). If you think of something to add to this, leave a comment.
Use OpenID.
I hate it when I have to enter the same data over and over again, and to think of new passwords because you (read: the website) likely store them as plaintext.
Oh, and please don't require me to give you a fake email.
Like this way www.soup.io/signup or the email way www.posterous.com or www.tripit.com