×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Sat, Nov 8, 2008 at 6:03 PM, John Allen <jallen@xxxxxxxxxxx> wrote:
I have a request to come up with a way to allow us to easily
enable or disable remote access by user
The best way to accomplish this is not on the IBM i itself, but
instead on the network level.
Most Firewall or VPN appliances allow custom policies to be set on a
user or group level. There are many protocols for central user
authentication and management. RADIUS is commong, also TACACS, or
direct LDAP.
This ensures that the is unable to access your IBM i on any way - be
it 5250, System i Access services, FTP, etc. pp.
Pay attention to your whole remote access strategy - locking the user
out from accessing your IBM i directly but still allowing access to a
TS Farm with System i Access installed nullifies whatever you've tried
to do. And remember that even a plain telnet client is enough for a
5250 login, some proxy servers could be abused with CONNECT to connect
to your IBM i (using a telnet client that supports HTTP proxies with
CONNECT, like putty), which would also circumvent the block.
midrange.com
