[KULRICE-13524] Rice Performance Client App Double Login Created: 21/Mar/14  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Quality Assurance
Affects Version/s: None
Fix Version/s: Backlog

Type: Task Priority: Major
Reporter: Daniel Seibert (Inactive) Assignee: Daniel Seibert (Inactive)
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: 1 day, 4 hours
Time Spent: Not Specified
Original Estimate: 1 day, 4 hours

Similar issues:
KULRICE-11774Create performance test environment: Standalone Server Oracle, Rice Sample App Client Oracle, KRAD Client Oracle
KULRICE-11775Create performance test environment: Standalone Server MySQL, KRAD Client MySQL, Rice Sample App Client MySQL
KULRICE-6749Configure rice sample app as a client app running against a standalone server
KULRICE-13348KRAD Client Sample App using standalone datasource instead of client
KULRICE-13536Add logout action to performance tests and KRAD Sample App AFTs
KULRICE-6122Create "Getting Started" guide for client app developers
KULRICE-1069simplify rice client app spring config
KULRICE-210Build a "rice client project template" for easy Rice client development
KULRICE-4040Rice DataDictionary files can "conflict" with Client app files.
KULRICE-6032Document introspector bugs and what that means for client apps
Rice Team: QA
Sprint: 2.4.0-rc1 QA Sprint 5, 2.4.0-rc1 QA Sprint 8

 Description   

On environments when a client application is using a separate standalone server, performing actions from the client app require logging into the client application, then also logging into the standalone server.



 Comments   
Comment by Adam Campbell (Inactive) [ 01/Apr/14 ]

the implementation of this task may change once Jerry replaces the dummy login filter with another filter that doesn't require visiting the login page - possibly within the next week or two

(this is per bi-weekly performance meeting 3/31/2014: https://docs.google.com/a/rsmart.com/document/d/1GNVY7OdLD9xe3lWrHBZieoSA1qgaNVXEdoVL6RShsBE/edit)

Generated at Wed Jul 15 00:19:09 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.