Automatic login, perhaps using command line options?

[pbumc]

Hi,

We're using PC 10.4 with the latest maintenance release.

Our users each have their own Windows login. Now we are implementing PowerChurch passwords, and they don't want to have to log in separately to PowerChurch (especially since they apparently can't specify their own passwords).

Can PowerChurch use Windows credentials for login (true "single sign-on")?

If not, can I supply the user name and password as command line parameters when starting PowerChurch? Then I could create a separate desktop icon for each user.

Thanks for your help,

Mark

[NeilZ]

Hi,

We're using PC 10.4 with the latest maintenance release.

Our users each have their own Windows login. Now we are implementing PowerChurch passwords, and they don't want to have to log in separately to PowerChurch (especially since they apparently can't specify their own passwords).

Can PowerChurch use Windows credentials for login (true "single sign-on")?

If not, can I supply the user name and password as command line parameters when starting PowerChurch? Then I could create a separate desktop icon for each user.

Thanks for your help,

Mark

There are no command line parameters for Powerchurch, as far as I know.

Actually, they can change their own passwords. Just have the Systems Administrator for Powerchurch setup their accounts with the permissions each one needs, and then create a temporary password for them to log in on.

Then here's the next steps:

1. User logs on using Temp Password.
2. User then accesses the FILE => PREFERENCES drop down menu from the menu bar and selects PASSWORDS
3. The next window will list their permissions in each area (they cannot change these), and will have an entry box at the bottom that says New Password. They can then change the password to whatever they want.

There is no worry about them forgetting the password, and not being able to recover it, as the System Admin for Powerchurch can grant a new temp password when necessary.

Hope this helps.

[pbumc]

Neil,

Thanks for the fast reply! When logged on as an end user, I see the Passwords dialog listing all the grayed-out permissions, but there is no New Password box. Is that something that I have to grant access to? (I have a screen shot but I don't see how to upload that here.)

Mark

[NeilZ]

Neil,

Thanks for the fast reply! When logged on as an end user, I see the Passwords dialog listing all the grayed-out permissions, but there is no New Password box. Is that something that I have to grant access to? (I have a screen shot but I don't see how to upload that here.)

Mark

Oh, I forgot. The System Admin has to grant each user the OK to change their own passwords.

[pbumc]

Oh, I forgot. The System Admin has to grant each user the OK to change their own passwords.

Finally found that under the "Utilities" tab. Thanks!

Mark

[C3HITServ]

Can PowerChurch be setup to use a Windows Primary Domain Controller (say a Samba server) for userid/password authentication?

[NeilZ]

Can PowerChurch be setup to use a Windows Primary Domain Controller (say a Samba server) for userid/password authentication?

The current version does not have this capability. The program maintains all module and database access using permissions set for each user and saved in that database.

I'm not sure that using a Window's authentication is that good an idea, as that would add another layer of complexity into the system. The system would have to query the controller to verify who the user is, then verify that the user is allowed access into Powerchurch and set the module access and database permissions for that user. The only thing missing is that the program need not store a password any longer.

IMHO ... Considering that many of the churches using Powerchurch are on a simple network, and share the program using network drive mapping, not many churches would use such a capability, thus it would not be cost effective for the developers to spend time trying to include a feature that perhaps 10% or less would use.

[C3HITServ]

Pros & cons understood. As we have grown beyond a few PCs to 10, and we consult with other churches on setting up similar environments, it becomes a necessity to have some common login (AAA) management. Just wondered if the hooks were there to use a PDC.

My alternative is to have people use a tool such as Roboform for password management, which they are for web accessed tools. I have not yet managed to get Roboform to work with PC+. Goal is that each user has a Roboform USB key (or installed on their PC) and then only have to know about their workstation password and one Roboform ID.

Thanks for the feedback!