How to generate hashed and salted user passwords for the PASOE transports or classic REST adapter in OE 11.7? - Progress Community

Loading

Skip to Main Content

How to generate hashed and salted user passwords for the PASOE transports or classic REST adapter in OE 11.7?

This article explains how to use extended local configurations for use an ABL application's runninf with PASOE or with the classic REST adapter in OpenEdge 11.7 onwards

May 2, 2018
Knowledge

Title

How to generate hashed and salted user passwords for the PASOE transports or classic REST adapter in OE 11.7?

URL Name

How-to-generate-hashed-and-salted-user-passwords-for-the-PASOE-transports-or-classic-REST-adapter-in-OE-11-7

Article Number

000122051

Environment

Product: OpenEdge Version: 11.7.x OS: All supported platforms

Question/Problem Description

How to generate hashed and salted user passwords for the classic REST Adapter and PASOE transports in OE 11.7?
How to generate hashed and salted user passwords for classic REST Management Agent and PASOE users?
How to generate hashed and salted user passwords for classic REST Application ans PASOE users?
How to implement hashed and salted user passwords using genspringpwd utility?
How to generate hashed and salted user passwords using genspringpwd utility?

Steps to Reproduce

Clarifying Information

Using the 'basic' authentication model.

With the classic REST adapter prior to OE 11.7, Progress Software recommended the Open Source software, Jacksum, to add user accounts with hashed and salted passwords in the users.properties file.
It was then necessary to edit the appSecurity-basic-local.xml file.

In 11.7 there is no appSecurity-basic-local.xml file to enable to achieve the same for the classic REST adapter or the PASOE REST transport.

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The classic REST adapter Spring configurations exist in 11.7.x PASOE, but in an updated architecture that does not require editing XML files. OpenEdge 11.7.x release uses Java style property and CSV files to accomplish the same Spring configuration, and in a way that custom tailoring is not overwritten when bug-fixes / updates are installed.

Conversion:

appSecurity-basic-local.xml ==> WEB-INF/oeablSecurity.properties & WEB-INF/oeablSecurity.csv

oeablSecurity.properties: Configures the login model and type of user account plug-in:

classic oeablSecurity.properties
appSecurity-basic-local.xml client.login.model=basic
http.all.authmanager=extlocal

Use ‘local’ for user accounts with unencrypted passwords
Use ‘extlocal’ for user accounts with encoded passwords.
What you had to download and use ‘jacksum’ in classic REST Spring configurations, you now use the DLC/bin/genspringpwd utility in 11.7.x PASOE. The 11.7.x PASOE Spring configuration uses a much stronger cryptographic algorithm (bcrypt) than the classic REST (sha1):

# generate pwd using stronger default bcrypt algorithm
DLC/bin/genspringpwd <clear-txt-pwd>

# generate same pwd using weaker sha1 algorithm
DLC/bin/genspringpwd <clear-txt-pwd> sha1

Note that both classic REST and PASOE use the same WEB-INF/users.properties file

Workaround

Notes

Progress Article:
How to generate hashed and salted user passwords for the REST Adapter prior to OpenEdge 11.7

References to Other Documentation:

Progress Application Server for OpenEdge: Administration Guide, Web application security configurations, User account configurations - Local and Extended Local user accounts
https://docs.progress.com/bundle/pas-for-openedge-administration-117/page/Local-and-Extended-Local-user-accounts.html

Keyword Phrase

Last Modified Date

4/13/2021 7:28 AM

OpenEdge General DiscussionsOpenEdge DeploymentOpenEdge DevelopmentOpenEdge RDBMSOpenEdge ArchitectureOpenEdge Pro2

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

How to generate hashed and salted user passwords for the PASOE transports or classic REST adapter in OE 11.7? - Progress Community