|
Posted by Roger Abell [MVP] on January 12, 2006, 4:01 am
Please log in for more thread options OK, let us dissect this a little.
The CORBA name server is just providing contact info.
The client uses that and gets challenged _by_the_application_
at the contact point (key point - it is not challenged by the machine)
but by the CORBA application.
Windows does similarly.
Clients quiry DNS for SRV records, or query AD for SPN of service.
This contact info is then used to attempt to access the service. The
service then, being a proper Kerberos application, triggers the normal
Kerberos ticket process to see if the client is allowed access to the
service.
Windows is coming to do this now more in the WS* based web services
pattern for many things moving forward.
> Hi,
> I have a server application working on a Windows 2003 Server (or
> Windows 2000 Server). This server application has got CORBA API. On the
> same machine CORBA Name Server is installed.
> Every client application first connects to the COBBA Name Server, gets
> information about server application (IP, port number). Having this
> information it connects to the server application on a known port
> (always the same).
> Has Windows 2003 server such posibility to let to connect to a specific
> port number only authorized users? For example if client application
> tries to connet to server on port number equal 123457 then server as it
> for login and password (for example domain login and password) .
> Is this or any similar in effect solution possible?
> Thx for any ideas:)
> Lolek1021
>
| 
XML Sitemap