Showing posts with label facing. Show all posts
Showing posts with label facing. Show all posts

Wednesday, March 28, 2012

Accessing profile info from Webservice

This is the situation I'm facing: I have a AutoCompleteExtender which fetches data based upon the information stored in Profile fields. When I write the code for the webservice connected to the Extender, I cannot access the data in asp.net's User Profiles. I have a suspicion this is because a web service is not really part of the website, but rather a standalone application.

Is there a way to use the Profile information in a web service?Nobody out there with an answer?
If the web services are part of the app, then there shouldn't be any domain access issues. Can you copy up your code?
I found out how to do it: apparently one needs to access the httpcontext in order to retrieve the Profile information:

Context.Profile["group.name"].ToString()

thank you for posting this!

i've been looking everywhere for such information, and even wrote a post on this board half hour ago after google groups search, but than came across your post and i will be able to sleep tonight.

thanks again!

Monday, March 26, 2012

Access credentials are not being loaded when use Atlas functionality

Facing this bizzare issue of access denied when use Atlas funcationality. I am using UpdatePanel in two .ascx controls that searches a list(list is on one .ascx and search button is on the 2nd .ascx).Everything works fine(i.e performs search in an Atlas way - no whol page refresh) but it generates an error on the browser that says..

A run time error has occured..

Line: 86762781

Error: Object expected.

When i see the log file at c:/windows/system32/Logfiles/ W3SVC1.. i see

That request is using 127.0.0.1 as the credentials instead of my own credential string.

This is the case if i use Atlas UpdatePanel otherwise it works fine.

Any clue in this regards, do i have to do something in terms of security to get it working?

Copied this Microsoft.Web.Atlas.dll over to my machine and issue went away.