• Subject: RE: Restricting User Access
  • From: "Cotes, Steven" <cotess@xxxxxxxxxxx>
  • Date: Mon, 17 Nov 1997 17:05:46 -0800

Chris,
before we get too far here.
First question is what Security Level are you running under ?

Next is, could you fill in a little more of what you need
to accomplish ?

Will this be an individual or group profile ?
If individual, do you really want to authorize them to
everything they need ? Group profiles and authorization
lists can really help in managing authority.

The first question is the most important. If you're at 10,
it can't be done. Above that, you can tighten it
down more at each level.

 -Steve Cotes
 -cotess@data-io.com

> ----------
> From:         Chris Ring[SMTP:cring@arksys.com]
> Sent:         Monday, November 17, 1997 1:44 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Restricting User Access
> 
> 
> Hello everyone!
> 
> I have a security question that some of you may be able to help me
> with.
> 
> Simply put -- Do you know if there is a way to create a user profile
> that
> is NOT authorized to anything?
> 
> I'm trying to set up a user ID on the '400 that basically is not
> authorized
> to anything.  I would like to then set up specific objects (pgms) that
> the
> user is authorized to.
> 
> Any help is greatly appreciated .....Thanks!
> 
> 
> Chris Ring
> Senior Systems Analyst
> Arksys Inc.
> Little Rock, Arkansas
> 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].