Alpha's Security and Updates to an app

[Tom Cone Jr]

Re: Alpha's Security and Updates to an app

Maybe someone should post a wishlist item so that developers have the option of storing groups and users in ordinary tables, with optional encryption. i.e. Using Alpha's security model give the developer an option on where the data is stored.

OK, I've posted the idea to the wishlist at IdeaScale.

Hopefully lots of folks will log in to "Agree". Right now its in 189th place on the "important to me" scale.

[DaveM]

Re: Alpha's Security and Updates to an app

Here is part of it that Tom Cone, Stan and others helped me with years ago.

dim global versionnumber as n
versionnumber = A5_GetAppVersionNumber()
dim global cpath as c
dim global cmast as c
dim global regusers as n
dim global runtimeusers as n
dim global totalusers as n

statusbar.hide()

cpath = a5.Get_Path()
cmast = a5.GET_MASTER_PATh()
regusers = a5_registration_license_inuse(cmast+"\sales.muf")
runtimeusers = a5_registration_license_inuse(cmast+"\sales.rmuf")
totalusers = runtimeusers+regusers+1

dim global scode as c
dim global stat as c = "A"
dim global username as c = ""
dim global salesman as c = ""
dim global cellphone as c = ""
dim global usernow as c = ""
dim global password as c = ""
dim global reverse as c = ""
dim global worknumber as n = 0
dim global secused as c = ""
dim global group as c = ""
dim global lot as c = ""
dim global nowpath as c = ""
dim global compbat as n = 0
dim global comptire as n = 0
dim global comptaxrate as n = 0
dim global comppred as n = 0
dim global complemon as n = 0
dim global comptags as n = 0
dim global comppmtterm as n = 0
dim global comptermtype as n = 0
dim global compapr as n = 0
dim global compnewwheels as n = 0
dim global compantitheft as n = 0
dim global permissions as c = ""
dim global userlot as c = ""
dim global cpath as c = ""
dim global electron as n = 0
dim global compdtaxrate as n = 0
dim global docrate as n = 0
dim global compname as c = ""
dim global gotoileads as L = .f.
dim global gotosales as L = .f.
dim global gotoother as L = .f.
dim global gotoreports as L = .f.
dim global gotocsi as L = .f.
dim global buycar as L = .f.
dim global gotoslsschedule as L = .f.
dim global gotoslslabels as L = .f.
dim global setupemail as L = .f.
dim global seedealnumbers as L = .f.
dim global reshadow as L = .f.
dim global gotocomp as L = .f.
dim global cleantbls as L = .f.
dim global compaddress as c = ""
dim global compcsz as c = ""
dim global gotoinv as L = .f.
dim global editletters as L = .f.
dim global gotoslspeople as L = .f.
dim global editownpassword as L = .f.
dim global editownuserinfo as L = .f.
dim global seeallslspeople as L = .f.
dim global editpermiss as L = .f.
dim global surl as c = "http://"
dim global gotovendors as L = .f.
dim global gotoagents as L = .f.
dim global gotorebates as L = .f.
dim global deletesales as L = .f.
dim global makebackup as L = .f.
dim global advertisers as L = .f.
dim global editcompinfo as L = .f.
dim global gotobanks as L = .f.
dim global addtrade as n = 0
dim global ulot as c = ""
dim global emok as L
dim global compphone as c
emok = .f.

'script_play_local("getstartup2")
:a5.minimize()

'=========================
x = getstart()

'=========================
lot = lotset
t=table.open("employ",file_ro_shared)
query.filter="username="+quote(trim(scode))
query.order=""
query.options="T"
ix=t.query_create()
if ix.records_get()=0 then
a5.close()
end if
ulot=t.lot
username=t.username
salesman=t.salesname
cellphone = t.cellphone
password = t.password
usernow = t.usernow
permissions = t.permissions
userlot = t.lot
gotoileads = t.gotoileads
gotosales = t.gotosales
gotoother = t.gotoother
gotoreports = t.gotoreports
gotocsi = t.gotocsi
buycar = t.buycar
gotoslsschedule = t.gotoslsschedule
gotoslslabels = t.gotoslslabels
setupemail = t.setupemail
seedealnumbers = t.seedealnumbers
reshadow = t.reshadow
gotocomp = t.gotocomp
cleantbls = t.cleantbls
gotoinv=t.gotoinv
editletters=t.Editletters
gotoslspeople = t.gotoslspeople
editownpassword = t.editownpassword
editownuserinfo=t.editownuserinfo
seeallslspeople=t.seeallslspeople
editpermiss=t.editpermiss
gotovendors=t.gotovendors
gotobanks=t.gotobanks
gotoagents=t.gotoagents
gotorebates=t.gotorebates
deletesales=t.deletesales
makebackup=t.makebackup
editcompinfo=t.editcompinfo
advertisers=t.advertisers
compbat = t.bat
comptire = t.tire
complemon = t.lemon
comptags = t.transfer
comppmtterm = t.term
comptermtype = t.termtype
compapr = t.apr
compnewwheels = t.newwheels
compantitheft = t.antitheft
t.close()

t=table.open("compa.dbf",file_ro_shared)
query.filter="lot="+s_quote(trim(lotset))
query.order=""
query.options="T"
ix=t.query_create()
lot=t.lot
group=t.group
comptaxrate=t.taxrate
compdtaxrate=t.dtaxrate
docrate=t.docrate
compname=t.name
compaddress=t.address
compcsz=t.cstzip
addtrade=t.addtrade
comppred=t.pred
electron=t.electron
compphone = t.phone
t.close()

:a5.maximize()
If PrintDailyReport = "Y" then
dim global leasemonths as n
leasemonths = 10

script_play_local("printstartreports")

end if
'topparent.Commit()
'topparent.Resynch()
'topparent.Refresh_Layout()
delete leasemonths
if alltrim(pword)<>alltrim(password) then
UI_MSG_BOX("User","Your User name or Password is incorrect. UpsLog will now close",UI_OK)
sleep(3)
a5.close()
end if
form.view("Begin")

FUNCTION getstart AS C ( )
Dim prmpt_title as c
dim prmpt_prompt as c
dim prmpt_default as c
Dim prmpt_title2 as c
dim prmpt_prompt2 as c
dim prmpt_default2 as c
'dim global pword as c
dim global perm as c
'dim global password as c

DIM global scode as C
DIM global pword as C
Dim global lotset as C = "1"
DIM global PrintDailyReport as C
DIM SHARED varC_result as C
printlist = "N"
footer_string = "Check the print box if you want to print the reports."
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Startup Check",<<%dlg%
{region}
User Code:| [.25scode];
password:| [%p%.25pword];
Lot to use:| [.5lotset];
;;
{region}Print List Daily Reports?:{endregion}|
{region}(PrintDailyReport:Y)
(PrintDailyReport:N){endregion};
;
{endregion};
{region}
{text=30,2:footer_string};
{endregion};
{line=1,0};
{region}
<15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%)

lotset = lotset
END FUNCTION

[Ronald Anusiewicz]

Re: Alpha's Security and Updates to an app

Thanks Dave,

I'll take a look at this.

[DaveM]

Re: Alpha's Security and Updates to an app

Ron,

Just trying to give back what was so freely given to me. I wrote it with help and have expended a number of times since v3(I think). It can be smaller or larger depending what you need.

At the time, Alpha had no security and users system at all. I think they started that about v7. I saw no reason to change and questions like yours exemplifies my reasoning.

[Ronald Anusiewicz]

Re: Alpha's Security and Updates to an app

Thanks Dave,

I have submitted a bug report. I'm not sure, but I think this could be a bug. Selwyn replied that he will look into this.

Ron

[Ray in Capetown]

Re: Alpha's Security and Updates to an app

Ron,
If you are still stuck on this. Or anyone else interested.
There is a solution. I just had the need and worked out a way to extract and restore user/group settings after an update.
I am just working on coding to run silently.

[Ray in Capetown]

Re: Alpha's Security and Updates to an app

In an update, the security is deeply embedded apparently in one or both of the .ALB and .ALM
I couldn't locate where, using hexadecimal search for a username nor master password, it may be encrypted.
Tom having shown interest here may have something to add to this below.

As far as I have got going using on both ends;-
...a5_security_option("DefineUsersandGroups"), the user must then select Export users/Groups, and then after update can Import from this dialogue. Or to send the resulting export file. It works in that the users groups are perfectly restored.
I thought I would be able to find out how to invoke the Alpha command/function but no luck, yet.
The file that is created a fairly uncomplicated text readable file. But that would only help if it could be automated for the client's system to email that across and include it with the update.

Or to get the client directly to the export/import dialogue would be an improvement. Possibly inserting keypresses to complete the selection??
Another thought to silently email the clients ALB and ALM, copy to another folder my side and do the export there.
Still a bit messy

[Ronald Anusiewicz]

Re: Alpha's Security and Updates to an app

Ray,

I submitted a bug report to Alpha. Selwyn did respond that they would look into it. But I never heard back.
I know they are busy with Alpha Anywhere so I just let it pass.

I just kicked the can down the road, but this may become an issue for me in the near future.
Thank you for your follow-up. I'll take a look at this myself.

Ron

[Ray in Capetown]

Re: Alpha's Security and Updates to an app

Great
First prize would be to get the operation that Alpha executes at the end, after final selection in the export or import dialog.
Then one could silently export and import before and after an update, or email the setup to put in to the update that is sent.
As you noted, the users/groups settings is not kept in any reference file.

We also cannot copy just the ALM and ALB in isolation to another database for the purpose of accessing to exporting the user info.

[Tim Kiebert]

Re: Alpha's Security and Updates to an app

The following idea I learned on this forum ages ago so I cannot remember who from and therefore can't give specific credit. I also have not used it it in practice myself but I have tested back then and I just did again and it still works.

Create a separate app just to hold the users and groups info. Set them up just as you would in your main app. Create this separate app in the same folder or a subfolder of the main app. Then when setting up security in the main app on the security dialog go to the 'Advanced Options' tab and choose 'Use shared user Account File' and then choose the separate app. Now as long as the updated main app you send to your customer points to that separate app their custom users will not get over written. In order for your end user to add users or groups provide a button/process that opens that separate app.

This probably won't suit everyone but thought I would throw it out there as an alternative.

[Ray in Capetown]

Re: Alpha's Security and Updates to an app

Thanks Tim
Two main complications there were A. getting it deployed and B. allowing client control of user/password changes from within the main app
The principle is correct but implementation overly complicated for both parties.
EDIT
But still a consideration. It may trump export / import depending on how often updates are sent against how often user setups change. My users seem often to do password changes and give operators temporary access to groups - switching apps a bit messy, but doable. I shall revisit that.

[Raymond Lyons]

Re: Alpha's Security and Updates to an app

Thanks Tim
Two main complications there were A. getting it deployed and B. allowing client control of user/password changes from within the main app
The principle is correct but implementation overly complicated for both parties.
EDIT
But still a consideration. It may trump export / import depending on how often updates are sent against how often user setups change. My users seem often to do password changes and give operators temporary access to groups - switching apps a bit messy, but doable. I shall revisit that.

Ray, I can't address your A (getting deployed) but years ago I did what Tim describes and though I don't remember the details now, I am certain I was able to give the client control of user/password changes from within the main app by building my own functions (and an Xdialog) to access user changes and passwords. That app is no longer being used but I probably still have a copy somewhere.

Raymond Lyons

[Raymond Lyons]

Re: Alpha's Security and Updates to an app

Ray, I can't address your A (getting deployed) but years ago I did what Tim describes and though I don't remember the details now, I am certain I was able to give the client control of user/password changes from within the main app by building my own functions (and an Xdialog) to access user changes and passwords. That app is no longer being used but I probably still have a copy somewhere.

Raymond Lyons

I can't find my old app. However, in thinking about it what I did may have been only similar to what Tim suggested, i.e., all my scripts and functions may have been stored in the other (otherwise empty) app. Thus when I updated script and functions it would have been to the other app, not the main one where security was. I think either approach would work, and since I can't right now find the old app I'm not sure which way I went. In any case, I do know I created my own interface to all aspects of the A5 system security and added other things to it such as creating a user table with data about the users, e.g., mobile number, etc. I'll look some more for the app when I get more time. Right now I am busy adding on to and remodeling our bathroom and can't spend a lot of time on this kind of thing.

Raymond Lyons

[Ray in Capetown]

Re: Alpha's Security and Updates to an app

Well Ray, you tried, thanks.
Luck with the bathroom.
Ray

[Ray in Capetown]

Re: Alpha's Security and Updates to an app

How simple the solution was. And it is completely seamless.
Create a new DB with nothing else but some security set on
Make a subfolder , copy it in. There are simply 4 files
In your primary system point security to that. All security ops are managed in the same way as the default methods.
That security db NEVER gets opened.

Initial install include that folder. Thereafter updates exclude it.
Changes on the user side remain unaffected.
In the attached browse shot - ACCTS\AC\PPP is the folder where the primary app resides. Its tiny and portable.