Forms Authentication Does Not Work in Sep CTP

Forms authentication still does not work in Sep CTP. I've been posting
questions in this forum for weeks and have received exactly 0 responses from
Microsoft. Do you guys even monitor this forum. There are lots of folks
trying to get forms authentication working and it sure does not help that you
took the 2000 instructions and just pasted them into the 2005 help file. I
get erros like:
Key cannot be null. Parameter name: key
which is not really helpful. I can't debug and find out what is causing the
error because I don't have the code. If you guys are so busy you can't
response to any of our questions then please just send me the source code to
report manager and reportingservices web server and I'll fix it for you so I
can get on with my life. I appologize if I'm a little terse but I've called
Microsoft offering to pay to get these issues resolved and I got the response
that I needed to be a BETA tester. So I became a BETA tester and then got
the response that the only interaction I have with MS is this newsgroup.
If there is a rouge MS developer out there willing to help me out just let
me know. Otherwise I can't really recommend my enterprise clients continue
down the SQL 2005 path.Zach,
Did you ever figure this out? I'm having the same problem with the RTM
version. I've got Forms Auth installed, I can register a user and login as
long as its not set as the adminUser. However, this user does not have any
rights to any reports. Also, I can't set the rights, because if I log in as
the admin user I get the same error message about "Key cannot be null.
Parameter name: key" Any suggestions from MS would be handy about now.
Jonathan Miller
webmaster@.accs.net
"Zach" wrote:
> Forms authentication still does not work in Sep CTP. I've been posting
> questions in this forum for weeks and have received exactly 0 responses from
> Microsoft. Do you guys even monitor this forum. There are lots of folks
> trying to get forms authentication working and it sure does not help that you
> took the 2000 instructions and just pasted them into the 2005 help file. I
> get erros like:
> Key cannot be null. Parameter name: key
> which is not really helpful. I can't debug and find out what is causing the
> error because I don't have the code. If you guys are so busy you can't
> response to any of our questions then please just send me the source code to
> report manager and reportingservices web server and I'll fix it for you so I
> can get on with my life. I appologize if I'm a little terse but I've called
> Microsoft offering to pay to get these issues resolved and I got the response
> that I needed to be a BETA tester. So I became a BETA tester and then got
> the response that the only interaction I have with MS is this newsgroup.
> If there is a rouge MS developer out there willing to help me out just let
> me know. Otherwise I can't really recommend my enterprise clients continue
> down the SQL 2005 path.|||Hi Jonathan,
Yes, I did finally figure it all out. The forms authentication sample code
shipped with the product has several bugs. There is also a bug in the sample
proxy for the web services calls. The key cannot be null error originates
from Authorization.GetPermissions. The problem is the base maps buit in
InitializeMaps are incorrect. You will have to make sure all available enum
entries are loaded into each map. You will also need to re-code the For Each
statements in GetPermissions to declare the variable oper as the correct type.
The bug in the Proxy class is in the GetWebResponse function. Change the
line that reads
AuthCookie = authCookie
to
Me.AuthCookie = authCookie
Hope this helps!
"Jonathan Miller" wrote:
> Zach,
> Did you ever figure this out? I'm having the same problem with the RTM
> version. I've got Forms Auth installed, I can register a user and login as
> long as its not set as the adminUser. However, this user does not have any
> rights to any reports. Also, I can't set the rights, because if I log in as
> the admin user I get the same error message about "Key cannot be null.
> Parameter name: key" Any suggestions from MS would be handy about now.
> Jonathan Miller
> webmaster@.accs.net
> "Zach" wrote:
> > Forms authentication still does not work in Sep CTP. I've been posting
> > questions in this forum for weeks and have received exactly 0 responses from
> > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > trying to get forms authentication working and it sure does not help that you
> > took the 2000 instructions and just pasted them into the 2005 help file. I
> > get erros like:
> >
> > Key cannot be null. Parameter name: key
> >
> > which is not really helpful. I can't debug and find out what is causing the
> > error because I don't have the code. If you guys are so busy you can't
> > response to any of our questions then please just send me the source code to
> > report manager and reportingservices web server and I'll fix it for you so I
> > can get on with my life. I appologize if I'm a little terse but I've called
> > Microsoft offering to pay to get these issues resolved and I got the response
> > that I needed to be a BETA tester. So I became a BETA tester and then got
> > the response that the only interaction I have with MS is this newsgroup.
> >
> > If there is a rouge MS developer out there willing to help me out just let
> > me know. Otherwise I can't really recommend my enterprise clients continue
> > down the SQL 2005 path.|||The demo code that ships is busted' That stinks. Is there anyway you can
zip up the fixed version and email it to me? webmaster@.accs.net
Thanks again!
"Zach" wrote:
> Hi Jonathan,
> Yes, I did finally figure it all out. The forms authentication sample code
> shipped with the product has several bugs. There is also a bug in the sample
> proxy for the web services calls. The key cannot be null error originates
> from Authorization.GetPermissions. The problem is the base maps buit in
> InitializeMaps are incorrect. You will have to make sure all available enum
> entries are loaded into each map. You will also need to re-code the For Each
> statements in GetPermissions to declare the variable oper as the correct type.
> The bug in the Proxy class is in the GetWebResponse function. Change the
> line that reads
> AuthCookie = authCookie
> to
> Me.AuthCookie = authCookie
> Hope this helps!
> "Jonathan Miller" wrote:
> > Zach,
> >
> > Did you ever figure this out? I'm having the same problem with the RTM
> > version. I've got Forms Auth installed, I can register a user and login as
> > long as its not set as the adminUser. However, this user does not have any
> > rights to any reports. Also, I can't set the rights, because if I log in as
> > the admin user I get the same error message about "Key cannot be null.
> > Parameter name: key" Any suggestions from MS would be handy about now.
> >
> > Jonathan Miller
> > webmaster@.accs.net
> >
> > "Zach" wrote:
> >
> > > Forms authentication still does not work in Sep CTP. I've been posting
> > > questions in this forum for weeks and have received exactly 0 responses from
> > > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > > trying to get forms authentication working and it sure does not help that you
> > > took the 2000 instructions and just pasted them into the 2005 help file. I
> > > get erros like:
> > >
> > > Key cannot be null. Parameter name: key
> > >
> > > which is not really helpful. I can't debug and find out what is causing the
> > > error because I don't have the code. If you guys are so busy you can't
> > > response to any of our questions then please just send me the source code to
> > > report manager and reportingservices web server and I'll fix it for you so I
> > > can get on with my life. I appologize if I'm a little terse but I've called
> > > Microsoft offering to pay to get these issues resolved and I got the response
> > > that I needed to be a BETA tester. So I became a BETA tester and then got
> > > the response that the only interaction I have with MS is this newsgroup.
> > >
> > > If there is a rouge MS developer out there willing to help me out just let
> > > me know. Otherwise I can't really recommend my enterprise clients continue
> > > down the SQL 2005 path.|||Hi Jonathan,
I also have the same problem opening the Sample Form Authentication.
Hope you don't mind to send the File that you have been fixed to me...
nicky_tsh@.hotmail.com
Thanks
Nicky
"Zach" wrote:
> Hi Jonathan,
> Yes, I did finally figure it all out. The forms authentication sample code
> shipped with the product has several bugs. There is also a bug in the sample
> proxy for the web services calls. The key cannot be null error originates
> from Authorization.GetPermissions. The problem is the base maps buit in
> InitializeMaps are incorrect. You will have to make sure all available enum
> entries are loaded into each map. You will also need to re-code the For Each
> statements in GetPermissions to declare the variable oper as the correct type.
> The bug in the Proxy class is in the GetWebResponse function. Change the
> line that reads
> AuthCookie = authCookie
> to
> Me.AuthCookie = authCookie
> Hope this helps!
> "Jonathan Miller" wrote:
> > Zach,
> >
> > Did you ever figure this out? I'm having the same problem with the RTM
> > version. I've got Forms Auth installed, I can register a user and login as
> > long as its not set as the adminUser. However, this user does not have any
> > rights to any reports. Also, I can't set the rights, because if I log in as
> > the admin user I get the same error message about "Key cannot be null.
> > Parameter name: key" Any suggestions from MS would be handy about now.
> >
> > Jonathan Miller
> > webmaster@.accs.net
> >
> > "Zach" wrote:
> >
> > > Forms authentication still does not work in Sep CTP. I've been posting
> > > questions in this forum for weeks and have received exactly 0 responses from
> > > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > > trying to get forms authentication working and it sure does not help that you
> > > took the 2000 instructions and just pasted them into the 2005 help file. I
> > > get erros like:
> > >
> > > Key cannot be null. Parameter name: key
> > >
> > > which is not really helpful. I can't debug and find out what is causing the
> > > error because I don't have the code. If you guys are so busy you can't
> > > response to any of our questions then please just send me the source code to
> > > report manager and reportingservices web server and I'll fix it for you so I
> > > can get on with my life. I appologize if I'm a little terse but I've called
> > > Microsoft offering to pay to get these issues resolved and I got the response
> > > that I needed to be a BETA tester. So I became a BETA tester and then got
> > > the response that the only interaction I have with MS is this newsgroup.
> > >
> > > If there is a rouge MS developer out there willing to help me out just let
> > > me know. Otherwise I can't really recommend my enterprise clients continue
> > > down the SQL 2005 path.|||Can I also get a copy of the corrected code?|||Can I also get a copy of the corrected code?
ebertsch@.gmail.com|||I am very interested in this code as well.
Thanks,
mdg
"ebertsch@.gmail.com" wrote:
> Can I also get a copy of the corrected code?
> ebertsch@.gmail.com
>|||I am interested in this code as well....
Thanks for help,
Mdg
"ebertsch@.gmail.com" wrote:
> Can I also get a copy of the corrected code?
> ebertsch@.gmail.com
>|||Could I please also ask for the corrected code?
clyons@.camsoftdata.com
Thanks!
"Zach" wrote:
> Hi Jonathan,
> Yes, I did finally figure it all out. The forms authentication sample code
> shipped with the product has several bugs. There is also a bug in the sample
> proxy for the web services calls. The key cannot be null error originates
> from Authorization.GetPermissions. The problem is the base maps buit in
> InitializeMaps are incorrect. You will have to make sure all available enum
> entries are loaded into each map. You will also need to re-code the For Each
> statements in GetPermissions to declare the variable oper as the correct type.
> The bug in the Proxy class is in the GetWebResponse function. Change the
> line that reads
> AuthCookie = authCookie
> to
> Me.AuthCookie = authCookie
> Hope this helps!
> "Jonathan Miller" wrote:
> > Zach,
> >
> > Did you ever figure this out? I'm having the same problem with the RTM
> > version. I've got Forms Auth installed, I can register a user and login as
> > long as its not set as the adminUser. However, this user does not have any
> > rights to any reports. Also, I can't set the rights, because if I log in as
> > the admin user I get the same error message about "Key cannot be null.
> > Parameter name: key" Any suggestions from MS would be handy about now.
> >
> > Jonathan Miller
> > webmaster@.accs.net
> >
> > "Zach" wrote:
> >
> > > Forms authentication still does not work in Sep CTP. I've been posting
> > > questions in this forum for weeks and have received exactly 0 responses from
> > > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > > trying to get forms authentication working and it sure does not help that you
> > > took the 2000 instructions and just pasted them into the 2005 help file. I
> > > get erros like:
> > >
> > > Key cannot be null. Parameter name: key
> > >
> > > which is not really helpful. I can't debug and find out what is causing the
> > > error because I don't have the code. If you guys are so busy you can't
> > > response to any of our questions then please just send me the source code to
> > > report manager and reportingservices web server and I'll fix it for you so I
> > > can get on with my life. I appologize if I'm a little terse but I've called
> > > Microsoft offering to pay to get these issues resolved and I got the response
> > > that I needed to be a BETA tester. So I became a BETA tester and then got
> > > the response that the only interaction I have with MS is this newsgroup.
> > >
> > > If there is a rouge MS developer out there willing to help me out just let
> > > me know. Otherwise I can't really recommend my enterprise clients continue
> > > down the SQL 2005 path.|||Just so you know - I never obtained that code so I can not forward it to you.
Thanks,
Michael Gardipee
"Chris_CamSoft" wrote:
> Could I please also ask for the corrected code?
> clyons@.camsoftdata.com
> Thanks!
>
> "Zach" wrote:
> > Hi Jonathan,
> >
> > Yes, I did finally figure it all out. The forms authentication sample code
> > shipped with the product has several bugs. There is also a bug in the sample
> > proxy for the web services calls. The key cannot be null error originates
> > from Authorization.GetPermissions. The problem is the base maps buit in
> > InitializeMaps are incorrect. You will have to make sure all available enum
> > entries are loaded into each map. You will also need to re-code the For Each
> > statements in GetPermissions to declare the variable oper as the correct type.
> >
> > The bug in the Proxy class is in the GetWebResponse function. Change the
> > line that reads
> > AuthCookie = authCookie
> > to
> > Me.AuthCookie = authCookie
> >
> > Hope this helps!
> >
> > "Jonathan Miller" wrote:
> >
> > > Zach,
> > >
> > > Did you ever figure this out? I'm having the same problem with the RTM
> > > version. I've got Forms Auth installed, I can register a user and login as
> > > long as its not set as the adminUser. However, this user does not have any
> > > rights to any reports. Also, I can't set the rights, because if I log in as
> > > the admin user I get the same error message about "Key cannot be null.
> > > Parameter name: key" Any suggestions from MS would be handy about now.
> > >
> > > Jonathan Miller
> > > webmaster@.accs.net
> > >
> > > "Zach" wrote:
> > >
> > > > Forms authentication still does not work in Sep CTP. I've been posting
> > > > questions in this forum for weeks and have received exactly 0 responses from
> > > > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > > > trying to get forms authentication working and it sure does not help that you
> > > > took the 2000 instructions and just pasted them into the 2005 help file. I
> > > > get erros like:
> > > >
> > > > Key cannot be null. Parameter name: key
> > > >
> > > > which is not really helpful. I can't debug and find out what is causing the
> > > > error because I don't have the code. If you guys are so busy you can't
> > > > response to any of our questions then please just send me the source code to
> > > > report manager and reportingservices web server and I'll fix it for you so I
> > > > can get on with my life. I appologize if I'm a little terse but I've called
> > > > Microsoft offering to pay to get these issues resolved and I got the response
> > > > that I needed to be a BETA tester. So I became a BETA tester and then got
> > > > the response that the only interaction I have with MS is this newsgroup.
> > > >
> > > > If there is a rouge MS developer out there willing to help me out just let
> > > > me know. Otherwise I can't really recommend my enterprise clients continue
> > > > down the SQL 2005 path.|||I will assume that you, as I, were working with the VB.NET version of the
sample. The C# version works. I found out the hard way and have posted my
unhappy feelings towards Microsoft for shipping a sample on their production
CD's that didn't work. The version I am working with is the actual release
and not a CTP.
"Mdg" wrote:
> Just so you know - I never obtained that code so I can not forward it to you.
> Thanks,
> Michael Gardipee
>
> "Chris_CamSoft" wrote:
> > Could I please also ask for the corrected code?
> >
> > clyons@.camsoftdata.com
> >
> > Thanks!
> >
> >
> > "Zach" wrote:
> >
> > > Hi Jonathan,
> > >
> > > Yes, I did finally figure it all out. The forms authentication sample code
> > > shipped with the product has several bugs. There is also a bug in the sample
> > > proxy for the web services calls. The key cannot be null error originates
> > > from Authorization.GetPermissions. The problem is the base maps buit in
> > > InitializeMaps are incorrect. You will have to make sure all available enum
> > > entries are loaded into each map. You will also need to re-code the For Each
> > > statements in GetPermissions to declare the variable oper as the correct type.
> > >
> > > The bug in the Proxy class is in the GetWebResponse function. Change the
> > > line that reads
> > > AuthCookie = authCookie
> > > to
> > > Me.AuthCookie = authCookie
> > >
> > > Hope this helps!
> > >
> > > "Jonathan Miller" wrote:
> > >
> > > > Zach,
> > > >
> > > > Did you ever figure this out? I'm having the same problem with the RTM
> > > > version. I've got Forms Auth installed, I can register a user and login as
> > > > long as its not set as the adminUser. However, this user does not have any
> > > > rights to any reports. Also, I can't set the rights, because if I log in as
> > > > the admin user I get the same error message about "Key cannot be null.
> > > > Parameter name: key" Any suggestions from MS would be handy about now.
> > > >
> > > > Jonathan Miller
> > > > webmaster@.accs.net
> > > >
> > > > "Zach" wrote:
> > > >
> > > > > Forms authentication still does not work in Sep CTP. I've been posting
> > > > > questions in this forum for weeks and have received exactly 0 responses from
> > > > > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > > > > trying to get forms authentication working and it sure does not help that you
> > > > > took the 2000 instructions and just pasted them into the 2005 help file. I
> > > > > get erros like:
> > > > >
> > > > > Key cannot be null. Parameter name: key
> > > > >
> > > > > which is not really helpful. I can't debug and find out what is causing the
> > > > > error because I don't have the code. If you guys are so busy you can't
> > > > > response to any of our questions then please just send me the source code to
> > > > > report manager and reportingservices web server and I'll fix it for you so I
> > > > > can get on with my life. I appologize if I'm a little terse but I've called
> > > > > Microsoft offering to pay to get these issues resolved and I got the response
> > > > > that I needed to be a BETA tester. So I became a BETA tester and then got
> > > > > the response that the only interaction I have with MS is this newsgroup.
> > > > >
> > > > > If there is a rouge MS developer out there willing to help me out just let
> > > > > me know. Otherwise I can't really recommend my enterprise clients continue
> > > > > down the SQL 2005 path.|||Actually, I was working with the C# code. The solution I implemented - in the
end - had me validating users against a custom provider (our SQL back end)
and that worked fine for us.
"Chris_CamSoft" wrote:
> I will assume that you, as I, were working with the VB.NET version of the
> sample. The C# version works. I found out the hard way and have posted my
> unhappy feelings towards Microsoft for shipping a sample on their production
> CD's that didn't work. The version I am working with is the actual release
> and not a CTP.
>
> "Mdg" wrote:
> > Just so you know - I never obtained that code so I can not forward it to you.
> >
> > Thanks,
> > Michael Gardipee
> >
> >
> > "Chris_CamSoft" wrote:
> >
> > > Could I please also ask for the corrected code?
> > >
> > > clyons@.camsoftdata.com
> > >
> > > Thanks!
> > >
> > >
> > > "Zach" wrote:
> > >
> > > > Hi Jonathan,
> > > >
> > > > Yes, I did finally figure it all out. The forms authentication sample code
> > > > shipped with the product has several bugs. There is also a bug in the sample
> > > > proxy for the web services calls. The key cannot be null error originates
> > > > from Authorization.GetPermissions. The problem is the base maps buit in
> > > > InitializeMaps are incorrect. You will have to make sure all available enum
> > > > entries are loaded into each map. You will also need to re-code the For Each
> > > > statements in GetPermissions to declare the variable oper as the correct type.
> > > >
> > > > The bug in the Proxy class is in the GetWebResponse function. Change the
> > > > line that reads
> > > > AuthCookie = authCookie
> > > > to
> > > > Me.AuthCookie = authCookie
> > > >
> > > > Hope this helps!
> > > >
> > > > "Jonathan Miller" wrote:
> > > >
> > > > > Zach,
> > > > >
> > > > > Did you ever figure this out? I'm having the same problem with the RTM
> > > > > version. I've got Forms Auth installed, I can register a user and login as
> > > > > long as its not set as the adminUser. However, this user does not have any
> > > > > rights to any reports. Also, I can't set the rights, because if I log in as
> > > > > the admin user I get the same error message about "Key cannot be null.
> > > > > Parameter name: key" Any suggestions from MS would be handy about now.
> > > > >
> > > > > Jonathan Miller
> > > > > webmaster@.accs.net
> > > > >
> > > > > "Zach" wrote:
> > > > >
> > > > > > Forms authentication still does not work in Sep CTP. I've been posting
> > > > > > questions in this forum for weeks and have received exactly 0 responses from
> > > > > > Microsoft. Do you guys even monitor this forum. There are lots of folks
> > > > > > trying to get forms authentication working and it sure does not help that you
> > > > > > took the 2000 instructions and just pasted them into the 2005 help file. I
> > > > > > get erros like:
> > > > > >
> > > > > > Key cannot be null. Parameter name: key
> > > > > >
> > > > > > which is not really helpful. I can't debug and find out what is causing the
> > > > > > error because I don't have the code. If you guys are so busy you can't
> > > > > > response to any of our questions then please just send me the source code to
> > > > > > report manager and reportingservices web server and I'll fix it for you so I
> > > > > > can get on with my life. I appologize if I'm a little terse but I've called
> > > > > > Microsoft offering to pay to get these issues resolved and I got the response
> > > > > > that I needed to be a BETA tester. So I became a BETA tester and then got
> > > > > > the response that the only interaction I have with MS is this newsgroup.
> > > > > >
> > > > > > If there is a rouge MS developer out there willing to help me out just let
> > > > > > me know. Otherwise I can't really recommend my enterprise clients continue
> > > > > > down the SQL 2005 path.