Drilldown Sample Issues

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

VBAHole22 - 28 Apr 2005 17:18 GMT

I am trying to get the first part of the drilldown sample to work (the
Authorization part). I get an error 'security token could not be
authenticated or authorized' every time I try to submit.
I have set up wse before but I overrode the AuthManager to hit against and
XML file.
This sample must be hitting against AD right? I should still be able to get
it to work though. I have added the joeblow user account on my machine and I
am sending in the request as machinename/joeblow and password. I have
verified the password is correct in the user account and joeblow is a member
of Users.
What else can I do to debug this?

Could it be that I am passing in the wrong username string? Would it matter
that this machine is not on a domain?
Any suggestions?

Reply to this Message

VBAHole22 - 28 Apr 2005 19:16 GMT

Well, I got a little more information. not an answer but a clue.
If I create a new web application and try to set a web reference to the
WeblogService it is not successful.
I get an error in the add web reference tool that looks up wsdls. It says
that the service could not be created. Is it possible this has something to
do with all of the phony urls that are in there?

> I am trying to get the first part of the drilldown sample to work (the
> Authorization part). I get an error 'security token could not be
[quoted text clipped - 11 lines]
> that this machine is not on a domain?
> Any suggestions?

Reply to this Message

John - 29 Apr 2005 21:46 GMT

I tried this sample code on my local machine (Both client and service located
in the same box) and only one example code does not work (Security policy). I
got a few error like you got but they are eventurally fixed by changing
configuration. Most of them are like follows:
1: import certs
2: Use cert tool to load certs
3: Set security to allow cert to be accessed from ASPNET and System accounts

If you follow the reame file that comes with the sample code. It should work.

However, I got a problem when run the SecurityPolicy code.
<UsePassword Type="wsse:PasswordText" wsp:Usage="wsp:Required" /> element is
not a child of <Claims>. I though the element missed
wssp: so I added it to the element (<wssp:UserPassword> and then I got error:
WSE407 ..... PasswordText is not a qualified element of
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3

I have no clue that how to fix this. Someone can help to give some clue?

> Well, I got a little more information. not an answer but a clue.
> If I create a new web application and try to set a web reference to the
[quoted text clipped - 18 lines]
> > that this machine is not on a domain?
> > Any suggestions?

Reply to this Message

VBAHole22 - 29 Apr 2005 23:42 GMT

I followed the directions to the letter and i am not even able to get past
the first part (authorize). I don't understand. But i think right now the
parts that I suspect are giving me issues are the AD part (maybe I am not in
a domain and it won't work) or the fact that the service itself doesn't work
because the urls are bogus.

> I tried this sample code on my local machine (Both client and service located
> in the same box) and only one example code does not work (Security policy). I
[quoted text clipped - 37 lines]
> > > that this machine is not on a domain?
> > > Any suggestions?

Reply to this Message

Drilldown Sample Issues

Free Magazines