Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0035770
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Web POSmajoralways2017-04-12 13:082017-04-25 10:52
ReporternataliagView Statuspublic 
Assigned ToRetail 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0035770: Auto login in web POS is not working

DescriptionWhen the Openbravo.properties is changed and the authentication.class is set as:
authentication.class=org.openbravo.authentication.basic.AutologonAuthenticationManager
authentication.autologon.username=Openbravo

The backend works correctly and the autologin is done using "Openbravo" but in webPOS it does not work. And it is not possible to do login anymore.
Steps To Reproduce1- Modify the Openbravo.properties of an environment and set the Authentication part as follows:
authentication.class=org.openbravo.authentication.basic.AutologonAuthenticationManager
authentication.autologon.username=Openbravo

2- Save it and compile the application
3- Go to backend url and the login is done automatically, which is correct.
4- Now, try it in the web POS. If you insert the webPOS url, the autologin does not work and the authentication is required.
5- When you try to login using the username and the password, an error is shown and it is not possible to enter.
 
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0096131)
marvintm (manager)
2017-04-24 13:11

Finally, for now we are considering this a design defect, and it's not even clear if we would want to fix it, as having a system perform auto-login is potentially insecure.

The implementation in the Web POS would have specific difficulties, such as interaction with the Terminal Authentication mechanism.

- Issue History
Date Modified Username Field Change
2017-04-12 13:08 nataliag New Issue
2017-04-12 13:08 nataliag Assigned To => Retail
2017-04-12 13:08 nataliag Resolution time => 1491170400
2017-04-12 13:08 nataliag Triggers an Emergency Pack => No
2017-04-12 13:45 marvintm Resolution time 1491170400 => 1493762400
2017-04-20 11:49 jorge-garcia Status new => scheduled
2017-04-20 11:49 jorge-garcia Assigned To Retail => jorge-garcia
2017-04-24 13:11 marvintm Resolution time 1493762400 =>
2017-04-24 13:11 marvintm Note Added: 0096131
2017-04-24 13:11 marvintm Type defect => design defect
2017-04-25 10:52 jorge-garcia Assigned To jorge-garcia => Retail
2017-04-25 10:52 jorge-garcia Status scheduled => acknowledged


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker