Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Prevent Command Line Access
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
265
Members:
0
Total:
265
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Prevent Command Line Access
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
andrew
Veteran Member
Posts: 100
6/6/2012 12:33 PM
windows 2003, sql 2005, still LAUA,
We are trying to prevent users from accessing the command line. We found a small "hole" in our setup.
When we setup a new user, use their AD login information and login to LID (interface desktop) -they go to a command prompt.
1. Once they do that lawson creates the print folder under LAUNT and we place a profile.bat file that automatically redirects them to a default token (which is fine).
The issue is the initial Login for the user - they still see the command line.
Now the chances that
1. Users still have LID on desktop is remote
2. users knows server name and port number is remote
BUT: for audit, there still is a remote chance that they can get to the command line.
The only way around this, is for the Lawson Admin to login as the user first (so the LAUNT is created) and the add the Profile.bat file
Does anyone have a different solution, so we can assure our audit team that no user (except admins) can get to a command line ?
apprecaite any assistance
Roger French
Veteran Member
Posts: 545
6/6/2012 1:28 PM
Usually in the cases I've seen, I.T. removes LID from user(s) desktop and prevents installation of LID on the user(s) desktop with corporate I.T. policy by putting them in an group which disallows/preventing launching or installation of LID; also preventing telnet-ing into Lawson environment. Also I.T. could use a port number for LID that is unknown to the user.
andrew
Veteran Member
Posts: 100
6/6/2012 3:37 PM
Thank you for your reply.
Yes have done a majority of those things - Did not think about GP rule. WIll look inot that option.
Appreciate it.
You are not authorized to post a reply.