Re: Authenticating against the i

[Mike <koldark@xxxxxxxxx>]

The programs I am interfacing with depend on the user to know what
authorities they have. This isn't a new from scratch app, I am trying to add
a web face to our RPGLE programs while keeping the business logic in RPG.

I have succeeded in doing this with one of our more simple programs to
interface with (an approval application). The last piece is to add user
authentication and bring it all together.

I'll be writing a post or two on IMHO on this when I get most of the pieces
of the puzzle together and working smoothly.

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark


On Tue, Nov 17, 2009 at 2:32 PM, Maurice O'Prey <maurice.oprey@xxxxxxxxx>wrote:

> I may be missing something here but wouldn't standard .NET not suffice? Try
> adding the following rule/s to your web.config file (some examples only
> included below). Using Deny users=? you could prevent any public (non
> authenticated) user from accessing any page/resource in the site, before
> they get anywhere near the iSeries?
> <!--
>                DIRECTORY AUTHORISATIONS
> -->
>        <!-- (Administrators only) -->
>        <location path="myAdminDirectory">
>                <system.web>
>                        <authorization>
>                                <allow roles="Administrator"/>
>                                <deny users="*"/>
>                        </authorization>
>                </system.web>
>        </location>
>  <!-- (Authenticated Users Only) -->
>        <location path="mySiteDirectory">
>                <system.web>
>                        <authorization>
>                                <deny users="?"/>
>                        </authorization>
>                </system.web>
>        </location>
>
> - Maurice
>
>
> -----Original Message-----
> From: systemidotnet-bounces@xxxxxxxxxxxx
> [mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
> Sent: 17 November 2009 19:24
> To: systemidotnet@xxxxxxxxxxxx
> Subject: Re: [SystemiDotNet] Authenticating against the i
>
> Thoughts:
>
> Create a connection string and pass the user ID and password entered by
> the user to this connection string. Then set a session variable and make
> sure each page checks the web session before displaying. This way NO
> page is public and you don't get past login page unless your connection
> is successful.
>
> I've also written stored procedures to call an iSeries program to
> authenticate, however you have to connect with a generic database
> user/password first.
>
> Regards,
> Richard Schoen
> RJS Software Systems Inc.
> "Get the information you need. Now!"
> Document Management, Workflow, Report Delivery, Forms and Business
> Intelligence
> Email: richard@xxxxxxxxxxxxxxx
> Web Site: http://www.rjssoftware.com
> Tel: (952) 736-5800
> Fax: (952) 736-5801
> Toll Free: (888) RJSSOFT
>
> ------------------------------
>
> message: 7
> date: Tue, 17 Nov 2009 11:14:45 -0600
> from: Mike <koldark@xxxxxxxxx>
> subject: Re: [SystemiDotNet] Authenticating against the i
>
> How do I secure the entire application? I don't have a need for a public
> side for this application?
>
> --
> Mike Wills
> http://mikewills.info
> P: (507) 933-0880 | Skype: koldark
>
>
>
> --
> This is the .net use with the System i (SystemiDotNet) mailing list
> To post a message email: SystemiDotNet@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
> or email: SystemiDotNet-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/systemidotnet.
>
> --
> This is the .net use with the System i (SystemiDotNet) mailing list
> To post a message email: SystemiDotNet@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
> or email: SystemiDotNet-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/systemidotnet.