> >I have a UserControl embedded in an aspx page that needs to access a
> >ws-security enabled web service.
[quoted text clipped - 27 lines]
> why is it insecure to post data onto a UserControl using https? Just
> make sure all pages are https://
Not all pages are https. Unfortunately.
> Second, you could use the Session Object, that's server side, so
> nobody would even know where to retrieve the userinformation. You
[quoted text clipped - 3 lines]
> "EnableViewState"'s to false and no info is posted back to the client;
> you would limit the potential, but that's another issue.
The user control accesses the web service directly and never posts to the
web server that served up the control. So all the view state stuff is not an
issue and there is no code behind.
> Third, you could try to create a single-page application. Just one
> WebForm, all your controls onto that form and handle all visible stuff
[quoted text clipped - 4 lines]
> wouldn't even have to use the Session-object, but you could keep all
> information in private static [string?] values.
I really don't understand that suggestion.
> Just some ideas...
>
> Leon
Thanks for your help.
The question is basically:
"How does a hosted user control (client side like ActiveX not a web user
control) get the credentials to pass to ws-security enabled web services."
Here is an example of an insecure way of doing it.
<object id="viewer" height="900" width="900"
classid="Test.dll#Test.TestControl">
<param name="username" value="user">
<param name="password" value="password">
</object
Leon Friesema - 29 Nov 2004 22:07 GMT
>> Third, you could try to create a single-page application. Just one
>> WebForm, all your controls onto that form and handle all visible stuff
[quoted text clipped - 20 lines]
> <param name="password" value="password">
></object>
Ahh, but that's not what I thought it was; I thought you ment a Web
User Control, not like this. In this case, I haven't got a clue what
to do ;-)
Anyway what I ment by creating a "single-page-application", not that
it's a solution to your problem, is one page with all WebUserControls
onto that one, so every page you call is actually the same page,
except with different visible WebUserControls (can be handled from the
code-behind). But then again: that's no solution to your question.
Leon.