294. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 10/4/2017 8:04:41 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

294.1 Files compared

#	Location	File	Last Modified
1	rdk.zip\rdk\product\tests\acceptance-tests\features	F133_authentication.feature	Mon Aug 21 12:51:01 2017 UTC
2	rdk.zip\rdk\product\tests\acceptance-tests\features	F133_authentication.feature	Tue Oct 3 20:16:15 2017 UTC

294.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	3	58
Changed	3	6
Inserted	0	0
Removed	0	0

294.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

294.4 Active regular expressions

No regular expressions were active.

294.5 Comparison detail

	1	@F133_auth entication _api
	2	Feature: F 133 - SDK VistA Writ e-Back Arc hitecture
	3
	4	#Authentic ation Reso urce Serve r
	5
	6	#Team Andr omeda
	7
	8	@F133_au thenticati on_api_1 @ US1835
	9	Scenario Outline: When a use r does aut henticatio n, then th is resourc e server i s called
	10	When t he client requests a uthenticat ion with a ccessCode "<accessco de>" and v erifyCode "<verifyco de>" and s ite "<site >" and div ision "<di vision>" a nd content Type "<con tenttype>"
	11	Then a successfu l response is return ed
	12	And th e authenti cation res ult contai ns
	13	\| fi eld \| value \|
	14	\| fi rstname \| PANORAMA \|
	15	\| la stname \| USER \|
	16	\| fa cility \| PANORAMA \|
	17	\| ti tle \| Clinicia n \|
	18	\| site \| R E D A CTED \|
	19	Exam ples:
	20	\| ac cesscode \| verify code \| s ite \| division \| content type \|
	21	\| REDACT \| REDACTED \| R E D A CTED \| 500 \| applicat ion/json \|
	22
	23	@F133_au thenticati on_api_2 @ US2990
	24	Scenario Outline: Authentica tion shoul d fail if both CPRS tab settin gs are fal se
	25	When t he client requests a uthenticat ion with a ccessCode "<accessco de>" and v erifyCode "<verifyco de>" and s ite "<site >" and div ision "<di vision>" a nd content Type "<con tenttype>"
	26	Then a n unauthor ized respo nse is ret urned
	27	And th e response contains error code
	28	\| fi eld \| value \|
	29	\| co de \| <code> \|
	30	Exam ples:
	31	\| ac cesscode \| verify code \| s ite \| division \| conten ttype \| code \|
	32	\| REDACT \| REDACT !! \| R E D A CTED \| 500 \| applicat ion/json \| 100.401. 1010 \|