| Author |
Message |
Ruben
Guest
|
 Posted:
Tue Jun 21, 2005 4:54 pm Post subject:
Mainframe Authentication in ASP.Net application |
|
|
We have a problem with asp.net application using IMS Connect component.
We check "Require client provided security" in the security tab in "Remote
Environments" Properties,
this will supply the ITOC some parameters, like Userid, password, OTMA group
and data store.
How can we provide these parameters to the ITOC?
Thank you,
Ruben |
|
| Back to top |
|
 |
Aaron Grady [MSFT]
Guest
|
| Posted:
Sat Jun 25, 2005 12:54 am Post subject:
Re: Mainframe Authentication in ASP.Net application |
|
|
Ruben-
In HIS 2004 there are two options. Your client application can create a
ClientContext object which it can fill with this information and pass to TI,
or you can use our ESSO (Enterprise Single Sign On) database to map Windows
accounts to mainframe accounts.
If you want to use the ClientContext object, you need to:
1. Make sure your TI method has the Use Context Parameter property set to
true.
2. Make sure your Remote Environment has "require client provided security"
checked.
3. Use the ClientContext object that gets registered in the GAC to write
entries into a client context object
4. Pass the client context object to the TI method call.
I would recommend you check out the C# Cedarbank client in the SDK for an
example of what you need to do. If you get stuck, please let us know.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <Ruben@discussions.microsoft.com> wrote in message
news:F2EC40D8-1116-43CD-85A0-5BE5C067B30C@microsoft.com...
| Quote: | We have a problem with asp.net application using IMS Connect component.
We check "Require client provided security" in the security tab in
"Remote
Environments" Properties,
this will supply the ITOC some parameters, like Userid, password, OTMA
group
and data store.
How can we provide these parameters to the ITOC?
Thank you,
Ruben |
|
|
| Back to top |
|
|
Ruben
Guest
|
| Posted:
Mon Jun 27, 2005 4:55 pm Post subject:
Re: Mainframe Authentication in ASP.Net application |
|
|
Thank you Aaron,
We used to set "clientcontext parameter" to FALSE!!!
That's why it doesn't work!!!
Bye
Ruben
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> ha scritto nel messaggio
news:e9iZ$RReFHA.544@TK2MSFTNGP12.phx.gbl...
| Quote: | Ruben-
In HIS 2004 there are two options. Your client application can create a
ClientContext object which it can fill with this information and pass to
TI,
or you can use our ESSO (Enterprise Single Sign On) database to map
Windows
accounts to mainframe accounts.
If you want to use the ClientContext object, you need to:
1. Make sure your TI method has the Use Context Parameter property set to
true.
2. Make sure your Remote Environment has "require client provided
security"
checked.
3. Use the ClientContext object that gets registered in the GAC to write
entries into a client context object
4. Pass the client context object to the TI method call.
I would recommend you check out the C# Cedarbank client in the SDK for an
example of what you need to do. If you get stuck, please let us know.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <Ruben@discussions.microsoft.com> wrote in message
news:F2EC40D8-1116-43CD-85A0-5BE5C067B30C@microsoft.com...
We have a problem with asp.net application using IMS Connect component.
We check "Require client provided security" in the security tab in
"Remote
Environments" Properties,
this will supply the ITOC some parameters, like Userid, password, OTMA
group
and data store.
How can we provide these parameters to the ITOC?
Thank you,
Ruben
|
|
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Wed Jun 29, 2005 11:44 pm Post subject:
Re: Mainframe Authentication in ASP.Net application |
|
|
Glad to hear that this is working for you now!
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <ruben.m@TOBEREMOVEDtiscali.it> wrote in message
news:utnPhuxeFHA.2076@TK2MSFTNGP15.phx.gbl...
| Quote: | Thank you Aaron,
We used to set "clientcontext parameter" to FALSE!!!
That's why it doesn't work!!!
Bye
Ruben
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> ha scritto nel
messaggio
news:e9iZ$RReFHA.544@TK2MSFTNGP12.phx.gbl...
Ruben-
In HIS 2004 there are two options. Your client application can create a
ClientContext object which it can fill with this information and pass to
TI,
or you can use our ESSO (Enterprise Single Sign On) database to map
Windows
accounts to mainframe accounts.
If you want to use the ClientContext object, you need to:
1. Make sure your TI method has the Use Context Parameter property set to
true.
2. Make sure your Remote Environment has "require client provided
security"
checked.
3. Use the ClientContext object that gets registered in the GAC to write
entries into a client context object
4. Pass the client context object to the TI method call.
I would recommend you check out the C# Cedarbank client in the SDK for an
example of what you need to do. If you get stuck, please let us know.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <Ruben@discussions.microsoft.com> wrote in message
news:F2EC40D8-1116-43CD-85A0-5BE5C067B30C@microsoft.com...
We have a problem with asp.net application using IMS Connect component.
We check "Require client provided security" in the security tab in
"Remote
Environments" Properties,
this will supply the ITOC some parameters, like Userid, password, OTMA
group
and data store.
How can we provide these parameters to the ITOC?
Thank you,
Ruben
|
|
|
| Back to top |
|
|
Ruben
Guest
|
| Posted:
Fri Jul 01, 2005 4:53 pm Post subject:
Re: Mainframe Authentication in ASP.Net application |
|
|
Dear Aaron,
It seems that we are expacting some errors involved with persistent
connection.
our development environment is MS Visual Studio .Net 2003
We would look for an example which explain how to use persistent connection
with IMS Connect...
When we send the host request the application returns the following error:
"(2167) The TCP transport received a socket error while attempting to
receive an IMS Connect or OTMA segment prefix. Check the HWS logs. Error
description: Connection reset by peer, expected length: 4. IP Address: XXX,
port: 6001, transid: LDGEST."
I've set up some TI traces and it seems that IMS Connect Socket closes the
connection too early...
We found an example on msdn @
http://msdn.microsoft.com/library/en-us/his_2004Main/htm/his_ti_developers_guide_uulv.asp
but it seems to use old components...
Is there any updated tutorial? C# CedarBank SDK sample is a little bit
difficoult.
We made some important steps forward... because of YOU!
Pls don't leave us alone :-)
Thanks,
Ruben
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> ha scritto nel messaggio
news:uH1CkqNfFHA.3780@TK2MSFTNGP10.phx.gbl...
| Quote: | Glad to hear that this is working for you now!
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <ruben.m@TOBEREMOVEDtiscali.it> wrote in message
news:utnPhuxeFHA.2076@TK2MSFTNGP15.phx.gbl...
Thank you Aaron,
We used to set "clientcontext parameter" to FALSE!!!
That's why it doesn't work!!!
Bye
Ruben
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> ha scritto nel
messaggio
news:e9iZ$RReFHA.544@TK2MSFTNGP12.phx.gbl...
Ruben-
In HIS 2004 there are two options. Your client application can create a
ClientContext object which it can fill with this information and pass
to
TI,
or you can use our ESSO (Enterprise Single Sign On) database to map
Windows
accounts to mainframe accounts.
If you want to use the ClientContext object, you need to:
1. Make sure your TI method has the Use Context Parameter property set
to
true.
2. Make sure your Remote Environment has "require client provided
security"
checked.
3. Use the ClientContext object that gets registered in the GAC to
write
entries into a client context object
4. Pass the client context object to the TI method call.
I would recommend you check out the C# Cedarbank client in the SDK for
an
example of what you need to do. If you get stuck, please let us know.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <Ruben@discussions.microsoft.com> wrote in message
news:F2EC40D8-1116-43CD-85A0-5BE5C067B30C@microsoft.com...
We have a problem with asp.net application using IMS Connect
component.
We check "Require client provided security" in the security tab in
"Remote
Environments" Properties,
this will supply the ITOC some parameters, like Userid, password,
OTMA
group
and data store.
How can we provide these parameters to the ITOC?
Thank you,
Ruben
|
|
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Wed Jul 06, 2005 8:52 pm Post subject:
Re: Mainframe Authentication in ASP.Net application |
|
|
Ruben-
Unfortunately persistent connections are not supported to IMS, so there's
not a lot I can be of help with. Here's a link to documentation on
persistent connections and which programming models are supported:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/his_2004Main/htm/his_ti_developers_guide_dgey.asp?frame=true
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <ruben.m@TOBEREMOVEDtiscali.it> wrote in message
news:ee0amrkfFHA.1412@TK2MSFTNGP09.phx.gbl...
| Quote: | Dear Aaron,
It seems that we are expacting some errors involved with persistent
connection.
our development environment is MS Visual Studio .Net 2003
We would look for an example which explain how to use persistent
connection
with IMS Connect...
When we send the host request the application returns the following error:
"(2167) The TCP transport received a socket error while attempting to
receive an IMS Connect or OTMA segment prefix. Check the HWS logs. Error
description: Connection reset by peer, expected length: 4. IP Address:
XXX,
port: 6001, transid: LDGEST."
I've set up some TI traces and it seems that IMS Connect Socket closes the
connection too early...
We found an example on msdn @
http://msdn.microsoft.com/library/en-us/his_2004Main/htm/his_ti_developers_guide_uulv.asp
but it seems to use old components...
Is there any updated tutorial? C# CedarBank SDK sample is a little bit
difficoult.
We made some important steps forward... because of YOU!
Pls don't leave us alone :-)
Thanks,
Ruben
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> ha scritto nel
messaggio
news:uH1CkqNfFHA.3780@TK2MSFTNGP10.phx.gbl...
Glad to hear that this is working for you now!
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <ruben.m@TOBEREMOVEDtiscali.it> wrote in message
news:utnPhuxeFHA.2076@TK2MSFTNGP15.phx.gbl...
Thank you Aaron,
We used to set "clientcontext parameter" to FALSE!!!
That's why it doesn't work!!!
Bye
Ruben
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> ha scritto nel
messaggio
news:e9iZ$RReFHA.544@TK2MSFTNGP12.phx.gbl...
Ruben-
In HIS 2004 there are two options. Your client application can create
a
ClientContext object which it can fill with this information and pass
to
TI,
or you can use our ESSO (Enterprise Single Sign On) database to map
Windows
accounts to mainframe accounts.
If you want to use the ClientContext object, you need to:
1. Make sure your TI method has the Use Context Parameter property set
to
true.
2. Make sure your Remote Environment has "require client provided
security"
checked.
3. Use the ClientContext object that gets registered in the GAC to
write
entries into a client context object
4. Pass the client context object to the TI method call.
I would recommend you check out the C# Cedarbank client in the SDK for
an
example of what you need to do. If you get stuck, please let us know.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruben" <Ruben@discussions.microsoft.com> wrote in message
news:F2EC40D8-1116-43CD-85A0-5BE5C067B30C@microsoft.com...
We have a problem with asp.net application using IMS Connect
component.
We check "Require client provided security" in the security tab in
"Remote
Environments" Properties,
this will supply the ITOC some parameters, like Userid, password,
OTMA
group
and data store.
How can we provide these parameters to the ITOC?
Thank you,
Ruben
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in