1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/os/security/authorisation/userpromptservice/test/tups/scripts/tups_integ.script Fri Jun 15 03:10:57 2012 +0200
1.3 @@ -0,0 +1,2555 @@
1.4 +//
1.5 +// Copyright (c) 2009-2010 Nokia Corporation and/or its subsidiary(-ies).
1.6 +// All rights reserved.
1.7 +// This component and the accompanying materials are made available
1.8 +// under the terms of the License "Eclipse Public License v1.0"
1.9 +// which accompanies this distribution, and is available
1.10 +// at the URL "http://www.eclipse.org/legal/epl-v10.html".
1.11 +//
1.12 +// Initial Contributors:
1.13 +// Nokia Corporation - initial contribution.
1.14 +//
1.15 +// Contributors:
1.16 +//
1.17 +// Description:
1.18 +//
1.19 +
1.20 +//tups_install
1.21 +//PRINT Run Basic test cases PREQ1262 for integration test
1.22 +
1.23 +//
1.24 +// Prepare various clones of TUPSInteg.exe with different SIDs.
1.25 +// Don't forget to delete clones at the end of test script.
1.26 +// but do not delete original one !!!!
1.27 +
1.28 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1c000 -SID 80001234 TUPSInteg_2.exe
1.29 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1c000 -SID 80002222 TUPSInteg_3.exe
1.30 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1c000 -SID 10004444 TUPSInteg_4.exe
1.31 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 810 -SID 10006666 TUPSInteg_allfiles_readdevice.exe
1.32 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 10 -SID 10007777 TUPSInteg_readdevice.exe
1.33 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 20 -SID 10008888 TUPSInteg_writedevice.exe
1.34 +RUN_PROGRAM 100 SETCAP TUPSInteg_data.exe 1cf00 -SID 101F7790 TUPSInteg_minor.exe
1.35 +
1.36 +// load suites
1.37 +LOAD_SUITE TUPSInteg_1
1.38 +LOAD_SUITE TUPSInteg_unprotected
1.39 +
1.40 +// load clones
1.41 +LOAD_SUITE TUPSInteg_2
1.42 +LOAD_SUITE TUPSInteg_3
1.43 +LOAD_SUITE TUPSInteg_4
1.44 +LOAD_SUITE TUPSInteg_allfiles_readdevice
1.45 +LOAD_SUITE TUPSInteg_readdevice
1.46 +LOAD_SUITE TUPSInteg_writedevice
1.47 +LOAD_SUITE TUPSInteg_minor
1.48 +
1.49 +
1.50 +//! @SYMTestCaseID SEC-UPS-MISC-0001
1.51 +//! @SYMTestCaseDesc Set up properties for policy evaluators and dialog creators, and Delete Existing Database
1.52 +
1.53 +START_TESTCASE SEC-UPS-MISC-0001
1.54 +
1.55 +RUN_TEST_STEP 100 TUPSInteg_1 PropertyStep z:\tups\integ\scripts\tups_properties.ini PropertiesToDestroy
1.56 +
1.57 +// Set up properties for policy evaluators and dialog creators.
1.58 +RUN_TEST_STEP 100 TUPSInteg_1 PropertyStep z:\tups\integ\scripts\tups_properties.ini PropertiesToCreate
1.59 +
1.60 +// Delete Existing Database
1.61 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.62 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.63 +
1.64 +END_TESTCASE SEC-UPS-MISC-0001
1.65 +
1.66 +
1.67 +//********************** SEC-UPS-A : BASIC USER PROMPTING **********************
1.68 +
1.69 +//! @SYMTestCaseID SEC-UPS-INTEG-A001
1.70 +//! @SYMTestCaseDesc User prompt service: option “only this session”
1.71 +//! (only_this_session)
1.72 +//!
1.73 +//! @SYMPREQ PREQ1262
1.74 +//! @SYMREQ REQ7367, REQ7410, REQ7411, REQ7412, REQ7413, REQ7414, REQ7415, REQ7417, REQ7446
1.75 +//! @SYMTestPriority Critical
1.76 +//! @SYMTestStatus Implemented
1.77 +//! @SYMTestActions Preconditions:
1.78 +//! • There is an appropriate policy, policy evaluator and dialog that matches the UID of the service
1.79 +//! offered by the “system server”.
1.80 +//!
1.81 +//!
1.82 +//! Test Actions:
1.83 +//! • Launch “test client” which tries to connect to a system server and use service.
1.84 +//! • System server asks for a user prompt to the UPS.
1.85 +//! • When UPS prompts user, select the “Only this session” option.
1.86 +//! • Check that now the “test client” can use the intended service from the “system server”.
1.87 +//! • Check again In same session that client still can use test service without need of user prompt.
1.88 +//! • Disconnect session and create new one.
1.89 +//! • Ask “test client” to request again for the same service to the system server. This should cause
1.90 +//! the service provided to request for a new user prompt.
1.91 +//! • Select again “Only this session” option.
1.92 +//! • Check that “test client” can use again the intended service from system server.
1.93 +//!
1.94 +//! @SYMTestExpectedResults • User prompt service dialog is displayed correctly in both occasions that “test client”
1.95 +//! request for authorisation.
1.96 +//! • Information displayed about the client is complete (see Appendix A).
1.97 +//! • “Test client” can use service from system server in both occasions after selecting “Only
1.98 +//! this session”
1.99 +//! • Information about the “Test client” is displayed correctly by user prompt.
1.100 +//! • Decision DB is not affected by previous operation as “only this session” is not expected to
1.101 +//! be stored.
1.102 +//!
1.103 +//! @SYMTestType CIT
1.104 +
1.105 +START_TESTCASE SEC-UPS-INTEG-A001
1.106 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini only_this_session
1.107 +END_TESTCASE SEC-UPS-INTEG-A001
1.108 +
1.109 +
1.110 +//! @SYMTestCaseID SEC-UPS-INTEG-A002
1.111 +//! @SYMTestCaseDesc User prompt service: User prompt service: option “never”
1.112 +//! (never)
1.113 +//!
1.114 +//! @SYMPREQ PREQ1262
1.115 +//! @SYMREQ REQ7367, REQ7372, REQ7374
1.116 +//!
1.117 +//! @SYMTestPriority Critical
1.118 +//! @SYMTestStatus Implemented
1.119 +//! @SYMTestActions Preconditions:
1.120 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.121 +//! service offered by the “system server”.
1.122 +//!
1.123 +//! Test Actions:
1.124 +//! • Launch “test client” which tries to connect to a system server and use service.
1.125 +//! • System server asks for a user prompt to the UPS.
1.126 +//! • When UPS prompts user, select the “Never” option.
1.127 +//! • Check that now the “test client” can NOT use the intended service after user selected “never”.
1.128 +//! • Disconnect session and create new one.
1.129 +//! • Ask “test client” to request again for the same service to the system server. System server should
1.130 +//! deny access to “test client” immediately without showing user prompt. Make sure that UPS was invoked
1.131 +//! again.
1.132 +//!
1.133 +//!
1.134 +//! @SYMTestExpectedResults • User prompt service dialog is displayed correctly.
1.135 +//! • Security dialog is displayed within one second (1 sec) of client request for service.
1.136 +//! • Information displayed about the client is complete (see Appendix A).
1.137 +//! • “Test client” can NOT use service from system server after selecting “Never”
1.138 +//! • Decision DB is updated correctly with the never decision.
1.139 +//! • The second time the “Test client” tries to access the service from the system server it
1.140 +//! should receive a silent denial.
1.141 +//!
1.142 +//! @SYMTestType CIT
1.143 +
1.144 +START_TESTCASE SEC-UPS-INTEG-A002
1.145 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini never
1.146 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.147 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini never_b
1.148 +END_TESTCASE SEC-UPS-INTEG-A002
1.149 +
1.150 +
1.151 +//! @SYMTestCaseID SEC-UPS-INTEG-A003
1.152 +//! @SYMTestCaseDesc User prompt service: option “Always”
1.153 +//! (always)
1.154 +//!
1.155 +//! @SYMPREQ PREQ1262
1.156 +//! @SYMREQ REQ7428, REQ7429, REQ7367, REQ7372, REQ7374, REQ7493
1.157 +//!
1.158 +//! @SYMTestPriority Critical
1.159 +//! @SYMTestStatus Implemented
1.160 +//! @SYMTestActions Preconditions:
1.161 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.162 +//! service offered by the “system server”.
1.163 +//! • Special: make sure that client have all necessary capabilities in order to test REQ7493
1.164 +//!
1.165 +//! Test Actions:
1.166 +//! • Launch “test client” which tries to connect to a system server and use service.
1.167 +//! • System server asks for a user prompt to the UPS.
1.168 +//! • When UPS prompts user, select the “Always” option.
1.169 +//! • Check in same session that now the “test client” now can use the intended service after user
1.170 +//! selected “Always”.
1.171 +//! • Ask “test client” to request again for the same service to the system server. System server should
1.172 +//! give immediate access to “test client” without showing user prompt (in same session).
1.173 +//! • Disconnect session and create new one.
1.174 +//! • Ask “test client” to request again for the same service to the system server. System server should
1.175 +//! give immediate access to “test client” without showing user prompt. Make sure that UPS was invoked
1.176 +//! again.
1.177 +//!
1.178 +//! @SYMTestExpectedResults • User prompt service dialog is displayed correctly.
1.179 +//! • Security dialog is displayed within one second (1 sec) of client request for service.
1.180 +//! • Information displayed about the client is complete (see Appendix A).
1.181 +//! • “Test client” can use service from system server after selecting “Always”
1.182 +//! • Decision DB is updated correctly with the Always decision.
1.183 +//! • The second time the “Test client” tries to access the service from the system server it
1.184 +//! should receive immediate access.
1.185 +//! • The response time from UPS for second use of test client is 100 ms (H4 board without demand
1.186 +//! paging)
1.187 +//!
1.188 +//! @SYMTestType CIT
1.189 +
1.190 +START_TESTCASE SEC-UPS-INTEG-A003
1.191 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini always
1.192 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.193 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini always_b
1.194 +END_TESTCASE SEC-UPS-INTEG-A003
1.195 +
1.196 +
1.197 +//! @SYMTestCaseID SEC-UPS-INTEG-A004
1.198 +//! @SYMTestCaseDesc User prompt service: “Yes” or “No” selection”
1.199 +//! (yes_or_no)
1.200 +//!
1.201 +//! @SYMPREQ PREQ1262
1.202 +//! @SYMREQ REQ7372
1.203 +//!
1.204 +//! @SYMTestPriority Critical
1.205 +//! @SYMTestStatus Implemented
1.206 +//! @SYMTestActions Preconditions:
1.207 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.208 +//! service offered by the “system server”.
1.209 +//! • Policy is set to display “yes” or “no” option
1.210 +//!
1.211 +//! Test Actions:
1.212 +//! • Launch “test client” which tries to connect to a system server and use service.
1.213 +//! • System server asks for a user prompt to the UPS.
1.214 +//! • When UPS prompts user, select the “yes” option.
1.215 +//! • Check that now the “test client” now can use the intended service.
1.216 +//! • In same session that before, request uses service.
1.217 +//! • UPS should prompt user again. Select yes
1.218 +//! • Launch “test client” in a new session. When security dialog is displayed select “no”.
1.219 +//! • Check that test client can not access intended service.
1.220 +//!
1.221 +//! @SYMTestExpectedResults • User prompt service dialog is displayed correctly.
1.222 +//! • Security dialog is displayed within one second (1 sec) of client request for service.
1.223 +//! • Information displayed about the client is complete (see Appendix A).
1.224 +//! • Decision DB does not store any new decision.
1.225 +//! • Access to test service is denied or granted accordingly.
1.226 +//!
1.227 +//! @SYMTestType CIT
1.228 +
1.229 +START_TESTCASE SEC-UPS-INTEG-A004
1.230 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini yes_or_no
1.231 +END_TESTCASE SEC-UPS-INTEG-A004
1.232 +
1.233 +
1.234 +
1.235 +//********************** SEC-UPS-B : USE CASES FOR UPS INVOLVING CONCURRENCY **********************
1.236 +
1.237 +
1.238 +//! @SYMTestCaseID SEC-UPS-INTEG-B004
1.239 +//! @SYMTestCaseDesc Concurrent process can access service despite unattended security dialog.
1.240 +//! (Unattended_Dialog)
1.241 +//!
1.242 +//! @SYMPREQ PREQ1262
1.243 +//! @SYMREQ REQ7427
1.244 +//!
1.245 +//! @SYMTestPriority Critical
1.246 +//! @SYMTestStatus Implemented
1.247 +//! @SYMTestActions Preconditions:
1.248 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.249 +//! service offered by the “system server”.
1.250 +//!
1.251 +//! Test Actions:
1.252 +//! • Launch 3 “test client” (A, B & C) which requests use of different system servers. Client A should
1.253 +//! not have any decision related to it stored in DB, Clients B should have a decision “Always” stored
1.254 +//! in DB, Client C should have decision “Never” stored in DB. Make sure that Client B & C are launch
1.255 +//! after security dialog is displayed for Client A.
1.256 +//! • Do not act in the security dialog for Client A when this one is displayed.
1.257 +//! • Check that Client B can access intended test service.
1.258 +//! • Check that Client C can not access intended test service and did receive a denial response.
1.259 +//! • Act now in security dialog for Client A, select “always”.
1.260 +//! • Check that Client A can access intended test service.
1.261 +//!
1.262 +//! @SYMTestExpectedResults • Final check in Decision DB shows 3 decisions stored: “Always” for Clients A & B, “Never”
1.263 +//! for Client C.
1.264 +//! • Accesses to service were granted for Clients A & B.
1.265 +//!
1.266 +//! @SYMTestType CIT
1.267 +
1.268 +START_TESTCASE SEC-UPS-INTEG-B004
1.269 +
1.270 +// Delete Existing Database
1.271 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.272 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.273 +
1.274 +// Setup up the Database so that Client B has an 'Always' Decision and Client C has a 'Never' Decision stored
1.275 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientB_Setup
1.276 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientC_Setup
1.277 +
1.278 +// Run 3 concurrent clients with a Coordinator to ensure that the Clients are synchronised
1.279 +CONCURRENT
1.280 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_Coordinator
1.281 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientA
1.282 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientB
1.283 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_ClientC
1.284 +CONSECUTIVE
1.285 +
1.286 +// Database Management Checks
1.287 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini Unattended_Dialog_dbManagementcheck
1.288 +
1.289 +END_TESTCASE SEC-UPS-INTEG-B004
1.290 +
1.291 +
1.292 +//! @SYMTestCaseID SEC-UPS-INTEG-B005
1.293 +//! @SYMTestCaseDesc Cancellation of UPS request in concurrent system server.
1.294 +//! (concurrent_cancellation)
1.295 +//!
1.296 +//! @SYMPREQ PREQ1262
1.297 +//! @SYMREQ REQ7427, REQ7431, REQ7432
1.298 +//!
1.299 +//! @SYMTestPriority Critical
1.300 +//! @SYMTestStatus Implemented
1.301 +//! @SYMTestActions Preconditions:
1.302 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.303 +//! service offered by the “system server”.
1.304 +//!
1.305 +//! Test Actions:
1.306 +//! • Launch 2 “test client” (A & B ) which requests use of different system servers. Client A
1.307 +//! should have a decision “Always” stored in DB, client B should have decision “Never” stored in DB.
1.308 +//! Client A & B run continuously and they request periodic use of a test service, each of this request
1.309 +//! should cause UPS to be invoked, UPS should continuously issue an appropriate silence response for A &
1.310 +//! B.
1.311 +//! • Launch “test client C” which requests use of different system servers. This client C does not have
1.312 +//! any related decision stored in DB.
1.313 +//! • The system server for client C is expected to request UPS for security dialog.
1.314 +//! • Do not act in security dialog displayed for client C, instead instruct system server for client C
1.315 +//! to cancel previous request made to UPS.
1.316 +//! • Make sure that clients A & B can still receive appropriate silent response from UPS despite
1.317 +//! cancellation of request by system server attending client C.
1.318 +//! • Launch test client D which should attempt use of same service attempted by client C. Security
1.319 +//! dialog should be displayed, select “Always”.
1.320 +//! • Check that client D can access intended service.
1.321 +//! • Launch client D in new session and check that it received silent acceptance.
1.322 +//!
1.323 +//!
1.324 +//! @SYMTestExpectedResults • Final check in Decision DB shows 2 decisions stored: “Always” for Clients A, “Never” for
1.325 +//! Client B.
1.326 +//! • Access to service was granted for Clients A & D.
1.327 +//! • Access to service was denied for Clients B.
1.328 +//!
1.329 +//! @SYMTestType CIT
1.330 +
1.331 +START_TESTCASE SEC-UPS-INTEG-B005
1.332 +
1.333 +// Delete Existing Database
1.334 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.335 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.336 +
1.337 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientA_setup
1.338 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientB_setup
1.339 +
1.340 +CONCURRENT
1.341 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientA
1.342 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientB
1.343 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientC_cancel
1.344 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientD
1.345 +CONSECUTIVE
1.346 +
1.347 +// Concurrent cancellation with UPS calling the same server, policy evaluator, dialog creator and policy from clients B + D
1.348 +CONCURRENT
1.349 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientA
1.350 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientB_samepolicy
1.351 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientC_cancel
1.352 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_cancellation_clientD_samepolicy
1.353 +CONSECUTIVE
1.354 +
1.355 +END_TESTCASE SEC-UPS-INTEG-B005
1.356 +
1.357 +
1.358 +//! @SYMTestCaseID SEC-UPS-INTEG-B008
1.359 +//! @SYMTestCaseDesc Early closure of client with concurrent processes, policy evaluator stage
1.360 +//! (client_dying_at_evaluator_point)
1.361 +//!
1.362 +//! @SYMPREQ PREQ1262
1.363 +//! @SYMREQ REQ7427
1.364 +//!
1.365 +//! @SYMTestPriority Critical
1.366 +//! @SYMTestStatus Implemented
1.367 +//! @SYMTestActions Preconditions:
1.368 +//! • There is an appropriate policy, policy evaluator and dialog creator that
1.369 +//! matches the UID of the service offered by the “system server”.
1.370 +//!
1.371 +//! Test Actions:
1.372 +//! • Launch 2 “test client” (A & B) which requests use of different system servers.
1.373 +//! Client A should have a decision “Always” stored in DB, client B should have
1.374 +//! decision “Never” stored in DB. Clients A & B run continuously and they request
1.375 +//! periodic use of a test service, each of this request should cause UPS to be
1.376 +//! invoked, UPS should continuously issue an appropriate silence response for A & B.
1.377 +//! • Launch “test client C” which requests use of a different system server. System
1.378 +//! server will invoke UPS and this one should invoke a policy evaluator. When
1.379 +//! policy evaluator is running shut down test client C.
1.380 +//! • Make sure that Clients A & B can still receive appropriate silent response from UPS.
1.381 +//!
1.382 +//! @SYMTestExpectedResults
1.383 +//! • Final check in Decision DB shows 2 decisions stored: “Always” for Clients A, “Never”
1.384 +//! for Client B.
1.385 +//! • Access to service was granted for Clients A.
1.386 +//! • Access to service was denied for Clients B & C.
1.387 +//!
1.388 +//! @SYMTestType CIT
1.389 +
1.390 +START_TESTCASE SEC-UPS-INTEG-B008
1.391 +
1.392 +// Delete Existing Database
1.393 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.394 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.395 +
1.396 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00a
1.397 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00b
1.398 +
1.399 +CONCURRENT
1.400 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini dying_client_at_evaluator_Coordinator
1.401 +RUN_TEST_STEP 100 TUPSInteg_minor DyingClient z:\tups\integ\scripts\tups_integ.ini dying_client_at_evaluator
1.402 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00a
1.403 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00b
1.404 +CONSECUTIVE
1.405 +
1.406 +// Database Management Checks
1.407 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini client_dying_at_evaluator_point_dbManagementCheck
1.408 +
1.409 +END_TESTCASE SEC-UPS-INTEG-B008
1.410 +
1.411 +
1.412 +
1.413 +//! @SYMTestCaseID SEC-UPS-B009
1.414 +//! @SYMTestCaseDesc Early closure of client with concurrent processes, dialog displayed stage
1.415 +//! (client_dying_at_dialog_point)
1.416 +//!
1.417 +//! @SYMPREQ PREQ1262
1.418 +//! @SYMREQ REQ7427
1.419 +//!
1.420 +//! @SYMTestPriority Critical
1.421 +//! @SYMTestStatus Implemented
1.422 +//! @SYMTestActions Preconditions:
1.423 +//! • There is an appropriate policy, policy evaluator and dialog creator that
1.424 +//! matches the UID of the service offered by the “system server”.
1.425 +//! Test Actions:
1.426 +//! • Launch 2 “test client” (A & B) which requests use of different system
1.427 +//! servers. Client A should have a decision “Always” stored in DB, client B
1.428 +//! should have decision “Never” stored in DB. Clients A & B run continuously and
1.429 +//! they request periodic use of a test service, each of this request should cause
1.430 +//! UPS to be invoked, UPS should continuously issue an appropriate silence response
1.431 +//! for A & B.
1.432 +//! • Launch “test client C” which requests use of a different system server. System
1.433 +//! server will invoke UPS and at some stage a security dialog will be invoked. When
1.434 +//! security dialog is displayed do not act on this one and shut down test client C.
1.435 +//! • Make sure that Clients A & B can still receive appropriate silent response from UPS.
1.436 +//!
1.437 +//! @SYMTestExpectedResults
1.438 +//! • Final check in Decision DB shows 2 decisions stored: “Always” for Clients A,
1.439 +//! “Never” for Client B.
1.440 +//! • Access to service was granted for Clients A.
1.441 +//! • Access to service was denied for Clients B & C.
1.442 +//!
1.443 +//! @SYMTestType CIT
1.444 +
1.445 +START_TESTCASE SEC-UPS-B009
1.446 +
1.447 +// Delete Existing Database
1.448 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.449 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.450 +
1.451 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00a
1.452 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_client_00b
1.453 +
1.454 +CONCURRENT
1.455 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini dying_client_at_dialog_Coordinator
1.456 +RUN_TEST_STEP 100 TUPSInteg_minor DyingClient z:\tups\integ\scripts\tups_integ.ini dying_client_at_dialog
1.457 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00a
1.458 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_client_00b
1.459 +CONSECUTIVE
1.460 +
1.461 +// Database Management Checks
1.462 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini client_dying_at_dialog_point_dbManagementCheck
1.463 +
1.464 +END_TESTCASE SEC-UPS-B009
1.465 +
1.466 +
1.467 +
1.468 +//! @SYMTestCaseID SEC-UPS-B010
1.469 +//! @SYMTestCaseDesc Multiple clients requesting multiple services in concurrent manner.
1.470 +//! (multiple_client_requests_concurrent)
1.471 +//!
1.472 +//! @SYMPREQ PREQ1262
1.473 +//! @SYMREQ REQ7427
1.474 +//!
1.475 +//! @SYMTestPriority Critical
1.476 +//! @SYMTestStatus Implemented
1.477 +//! @SYMTestActions Preconditions:
1.478 +//! • As set in test assumptions section on detail description of this test.
1.479 +//!
1.480 +//! Test Actions:
1.481 +//! • Execute test actions as set in “tests sequence part 1” above.
1.482 +//! • Execute test actions as set in “tests sequence part 2” above.
1.483 +//! • Reset test clients and test system servers.
1.484 +//! • Execute test actions as set in “tests sequence part 3” above.
1.485 +//!
1.486 +//! @SYMTestExpectedResults Test services are granted/denied accordingly as set in detail test description.
1.487 +//!
1.488 +//! @SYMTestType CIT
1.489 +
1.490 +START_TESTCASE SEC-UPS-B010
1.491 +
1.492 +// Delete Existing Database
1.493 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.494 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.495 +
1.496 +CONCURRENT
1.497 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client1
1.498 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client2
1.499 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client3
1.500 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client4
1.501 +CONSECUTIVE
1.502 +
1.503 +CONCURRENT
1.504 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client1
1.505 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client2
1.506 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client3
1.507 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client4
1.508 +CONSECUTIVE
1.509 +
1.510 +// Close and Reset UPS
1.511 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.512 +
1.513 +CONCURRENT
1.514 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client1
1.515 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client2
1.516 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client3
1.517 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini concurrent_multiple_request_client4
1.518 +CONSECUTIVE
1.519 +
1.520 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini count_24
1.521 +
1.522 +END_TESTCASE SEC-UPS-B010
1.523 +
1.524 +
1.525 +//! @SYMTestCaseID SEC-UPS-B011
1.526 +//! @SYMTestCaseDesc Multiple clients requesting multiple services in non–concurrent manner.
1.527 +//! (multiple_client_requests_consecutive)
1.528 +//!
1.529 +//! @SYMPREQ PREQ1262
1.530 +//! @SYMREQ REQ****
1.531 +//!
1.532 +//! @SYMTestPriority Critical
1.533 +//! @SYMTestStatus Implemented
1.534 +//! @SYMTestActions Preconditions:
1.535 +//! • As set for test case SEC-UPS-B002C, but each test client and system server do not run concurrently
1.536 +//! with other tests clients.
1.537 +//!
1.538 +//! Test Actions:
1.539 +//! • Execute test actions as set in “tests sequence part 1” on test case SEC-UPS-B010 above.
1.540 +//! • Execute test actions as set in “tests sequence part 2” on test case SEC-UPS-B010 above.
1.541 +//! • Reset test clients and test system servers.
1.542 +//! • Execute test actions as set in “tests sequence part 3” on test case SEC-UPS-B010 above.
1.543 +//!
1.544 +//! @SYMTestExpectedResults Test services are granted/denied accordingly as set in detail test description for test case
1.545 +//! SEC-UPS-B010 above.
1.546 +//!
1.547 +//! @SYMTestType CIT
1.548 +
1.549 +START_TESTCASE SEC-UPS-B011
1.550 +
1.551 +// Delete Existing Database
1.552 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.553 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.554 +
1.555 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client1_Part1
1.556 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client2_Part1
1.557 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client3_Part1
1.558 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client4
1.559 +
1.560 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client1_Part2
1.561 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client2_Part2
1.562 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client3_Part2
1.563 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client4
1.564 +
1.565 +// Close and Reset UPS
1.566 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.567 +
1.568 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client1_Part2
1.569 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client2_Part2
1.570 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client3_Part2
1.571 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini multiple_request_client4
1.572 +
1.573 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini count_24
1.574 +
1.575 +END_TESTCASE SEC-UPS-B011
1.576 +
1.577 +
1.578 +
1.579 +//! @SYMTestCaseID SEC-UPS-INTEG-B012
1.580 +//! @SYMTestCaseDesc Concurrent process can access service despite multiple unattended security dialogs.
1.581 +//! (Multiple_Unattended_Dialogs)
1.582 +//!
1.583 +//! @SYMPREQ PREQ1262
1.584 +//! @SYMREQ REQ7427
1.585 +//!
1.586 +//! @SYMTestPriority Critical
1.587 +//! @SYMTestStatus Implemented
1.588 +//! @SYMTestActions Preconditions:
1.589 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the service offered by the “system
1.590 +//! server”.
1.591 +//!
1.592 +//! Test Actions:
1.593 +//! • Launch 3 “test client” (A, B & C) which requests use of different system servers. Clients A & B should not have any decision
1.594 +//! related to it stored in DB, Clients C should have a decision “Always” stored in DB. Make sure that Client B is launched after
1.595 +//! security dialog is displayed for Client A. Make sure that request for security dialog for client B is made before client C is
1.596 +//! launched.
1.597 +//! • Do not act in the security dialog for Client A when this one is displayed.
1.598 +//! • Check that Client C can access intended test service and UPS did issue a silent acceptance to system server from UPS for the
1.599 +//! request made for client C.
1.600 +//! • Act now in security dialog for Client A, select “Never”.
1.601 +//! • Check that Client A can NOT access intended test service.
1.602 +//! • Act now in security dialog for Client B, select “Always”.
1.603 +//! • Check that Client B can access intended test service.
1.604 +//!
1.605 +//! @SYMTestExpectedResults • Final check in Decision DB shows 4 decisions stored: “Always” for Clients B & C. “Never” for Client A.
1.606 +//! • Accesses to service were granted for Clients B & C.
1.607 +//!
1.608 +//! @SYMTestType CIT
1.609 +
1.610 +START_TESTCASE SEC-UPS-INTEG-B012
1.611 +
1.612 +// Delete Existing Database
1.613 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.614 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.615 +
1.616 +// Setup up the Database so that Client C has an 'Always' Decision stored
1.617 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Multiple_Unattended_Dialogs_ClientC_Setup
1.618 +
1.619 +// Run 3 concurrent clients with a Coordinator to ensure that the Clients are synchronised
1.620 +CONCURRENT
1.621 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini Multiple_Unattended_Dialogs_Coordinator
1.622 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Multiple_Unattended_Dialogs_ClientA
1.623 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Multiple_Unattended_Dialogs_ClientB
1.624 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Multiple_Unattended_Dialogs_ClientC
1.625 +CONSECUTIVE
1.626 +
1.627 +// Database Management Checks
1.628 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini Multiple_Unattended_Dialogs_dbManagementcheck
1.629 +
1.630 +END_TESTCASE SEC-UPS-INTEG-B012
1.631 +
1.632 +
1.633 +//********************** SEC-UPS-C : DIALOG SERIALISATION SPECIFIC TESTS **********************
1.634 +
1.635 +
1.636 +//! @SYMTestCaseID SEC-UPS-C001
1.637 +//! @SYMTestCaseDesc Dialog serialisation
1.638 +//! (Dialog_Serialisation)
1.639 +//!
1.640 +//! @SYMPREQ PREQ1262
1.641 +//! @SYMREQ REQ7472
1.642 +//!
1.643 +//! @SYMTestPriority Critical
1.644 +//! @SYMTestStatus Implemented
1.645 +//! @SYMTestActions Preconditions:
1.646 +//! • For each of the services There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the service //! offered by the “system server”.
1.647 +//!
1.648 +//! Test Actions:
1.649 +//! • Launch 3 “test client” (A ,B & C) in turns, these Clients requests use of a system server. System server should request prompt of //! security dialog to UPS. Make sure that requests for the 3 security dialog are made before acting in the first dialog that is expected //! to be displayed.
1.650 +//! • For first security dialog to be displayed (client A) select “always”.
1.651 +//! • Check that client A can access intended service.
1.652 +//! • For second security dialog to be displayed (client B) select “only this session”.
1.653 +//! • Check that client B can access intended service.
1.654 +//! • For third security dialog to be displayed (client C) select “never”.
1.655 +//! • Check that client C can NOT access intended service.
1.656 +//! • Shut down clients and servers.
1.657 +//! • Launch client A again, check that it can access test service and UPS is issuing silent acceptance.
1.658 +//! • Launch client C again, check that it can access test service and UPS is issuing silent denial.
1.659 +//!
1.660 +//!
1.661 +//! @SYMTestExpectedResults • User prompt service dialogs are displayed correctly, and only 1 dialog at any time.
1.662 +//! • Information displayed about the client is complete (see Appendix A).
1.663 +//! • Clients A & C can access test service.
1.664 +//! • Client B can not access test service.
1.665 +//! •Decision DB is updated correctly with the Always decision.
1.666 +//!
1.667 +//! @SYMTestType CIT
1.668 +
1.669 +START_TESTCASE SEC-UPS-C001
1.670 +
1.671 +// Delete Existing Database
1.672 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.673 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.674 +
1.675 +// Run 3 concurrent clients with a Coordinator to ensure that the Clients are synchronised
1.676 +CONCURRENT
1.677 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_Coordinator
1.678 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_clientA
1.679 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_clientB
1.680 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_clientC
1.681 +CONSECUTIVE
1.682 +
1.683 +// Silent acceptance checking for Client A
1.684 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_clientA_DecisionCheck
1.685 +
1.686 +// Silent denial checking for Client C
1.687 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_clientC_DecisionCheck
1.688 +
1.689 +// Database Management Checks
1.690 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini Dialog_Serialisation_dbManagementcheck
1.691 +
1.692 +END_TESTCASE SEC-UPS-C001
1.693 +
1.694 +
1.695 +//! @SYMTestCaseID SEC-UPS-INTEG-C005
1.696 +//! @SYMTestCaseDesc To ensure that a cancellation of a user prompt dialog (cancel button) does not affect
1.697 +//! adversatively the behaviour of the UPS.
1.698 +//! (single_dialog_cancellation)
1.699 +//!
1.700 +//! @SYMPREQ PREQ1262
1.701 +//! @SYMREQ REQ7427
1.702 +//!
1.703 +//! @SYMTestPriority Critical
1.704 +//! @SYMTestStatus Implemented
1.705 +//! @SYMTestActions Preconditions:
1.706 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of
1.707 +//! the service offered by the “system server”.
1.708 +//!
1.709 +//! Test Actions:
1.710 +//! • Launch a “test client A” which requests use of a system server.
1.711 +//! • System server asks for a user prompt to the UPS.
1.712 +//! • When security dialog is displayed, cancel request made from system server to UPS, this should
1.713 +//! cause cancellation of notifier and therefore cancellation of security dialog.
1.714 +//! • Close test client A.
1.715 +//! • Launch test client B which tries to use the same test service.
1.716 +//! • System server requests security dialog.
1.717 +//! • When dialog is displayed select “always”
1.718 +//! • Check that client B can use test service.
1.719 +//!
1.720 +//! @SYMTestExpectedResults
1.721 +//! • User prompt service dialogs is displayed correctly.
1.722 +//! • Cancellation of security dialog does not cause UPS malfunction.
1.723 +//! • Decision DB is upgraded with new decision for test client B.
1.724 +//!
1.725 +//! @SYMTestType CIT
1.726 +//!
1.727 +
1.728 +
1.729 +START_TESTCASE SEC-UPS-INTEG-C005
1.730 +
1.731 +// Delete Existing Database
1.732 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.733 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.734 +
1.735 +// Client A is run concurrently with a Coordinator so that the request can be cancelled once the Dialog Creator has been invoked
1.736 +CONCURRENT
1.737 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini single_dialog_cancellation_Coordinator
1.738 +RUN_TEST_STEP 100 TUPSInteg_minor CancelPrompt z:\tups\integ\scripts\tups_integ.ini single_dialog_cancellation_ClientA
1.739 +CONSECUTIVE
1.740 +
1.741 +// Client B makes an attempt to access the same service as Client A
1.742 +RUN_TEST_STEP 100 TUPSInteg_minor SimpleRequest z:\tups\integ\scripts\tups_integ.ini single_dialog_cancellation_ClientB
1.743 +
1.744 +// Database Management Checks
1.745 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini single_dialog_cancellation_dbManagementCheck
1.746 +
1.747 +END_TESTCASE SEC-UPS-INTEG-C005
1.748 +
1.749 +
1.750 +
1.751 +//! @SYMTestCaseID SEC-UPS-INTEG-C006
1.752 +//! @SYMTestCaseDesc Cancellation of first dialog from a queue of pending security dialogs.
1.753 +//! (cancellation_first_dialog)
1.754 +//!
1.755 +//! @SYMPREQ PREQ1262
1.756 +//! @SYMREQ REQ7431 REQ7432
1.757 +//!
1.758 +//! @SYMTestPriority Critical
1.759 +//! @SYMTestStatus Implemented
1.760 +//! @SYMTestActions Preconditions:
1.761 +//! • For each of the services there is an appropriate policy, policy evaluator and dialog creator that matches the UID of the service //! offered by the “system server”.
1.762 +//!
1.763 +//! Test Actions:
1.764 +//! • Launch 3 “test client” in turns (A,B & C), these Clients try to use of a test service in system server.
1.765 +//! • Make sure system server has request security dialog for all clients before acting in any security dialog.
1.766 +//! • Once user prompt is displayed for client A, induce system server to cancel request to UPS for client A, this should cause security //! dialog for client A to be removed from screen.
1.767 +//! • Security dialog for client B should appear on screen select “never” and check that application can NOT use intended service.
1.768 +//! • Security dialog for client C should appear on screen select “always” and check that application can use intended service.
1.769 +//!
1.770 +//! @SYMTestExpectedResults • Decision DB is upgraded with new decisions for Clients B (“never”) and C (“always”)
1.771 +//! • UPS does not malfunction after cancellation of dialog for Client A.
1.772 +//!
1.773 +//! @SYMTestType CIT
1.774 +//!
1.775 +
1.776 +
1.777 +START_TESTCASE SEC-UPS-INTEG-C006
1.778 +
1.779 +// Delete Existing Database
1.780 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.781 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.782 +
1.783 +// Client A, B and C are run concurrently with a Coordinator so that the first dialog (Client A) can be cancelled once all of the service requests
1.784 +// have been invoked
1.785 +CONCURRENT
1.786 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini cancellation_first_dialog_Coordinator
1.787 +RUN_TEST_STEP 100 TUPSInteg_minor CancelPrompt z:\tups\integ\scripts\tups_integ.ini cancellation_first_dialog_ClientA_cancel
1.788 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_first_dialog_ClientB
1.789 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_first_dialog_ClientC
1.790 +CONSECUTIVE
1.791 +
1.792 +// Database Management Checks
1.793 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini cancellation_first_dialog_dbManagementCheck
1.794 +
1.795 +END_TESTCASE SEC-UPS-INTEG-C006
1.796 +
1.797 +
1.798 +
1.799 +//! @SYMTestCaseID SEC-UPS-INTEG-C007
1.800 +//! @SYMTestCaseDesc Cancellation of last dialog from a queue of pending security dialogs.
1.801 +//! (cancellation_last_dialog)
1.802 +//!
1.803 +//! @SYMPREQ PREQ1262
1.804 +//! @SYMREQ REQ7431 REQ7432
1.805 +//!
1.806 +//! @SYMTestPriority Critical
1.807 +//! @SYMTestStatus Implemented
1.808 +//! @SYMTestActions Preconditions:
1.809 +//! • For each of the services there is an appropriate policy, policy evaluator and dialog creator that matches the UID of the service //! offered by the “system server”.
1.810 +//!
1.811 +//! Test Actions:
1.812 +//! • Launch 3 “test client” in turns (A, B & C), these Clients try to use of a test service in system server.
1.813 +//! • Make sure system server has request security dialog for all clients before acting in any security dialog.
1.814 +//! • Security dialog for client A should appear on screen select “always” and check that application can use intended service.
1.815 +//! • Security dialog for client B should appear on screen select “never” and check that application can NOT use intended service.
1.816 +//! • Once user prompt is displayed for client C, induce system server to cancel request to UPS for client C, this should cause security //! dialog for client C to be removed from screen.
1.817 +//! • In new session ask client A to try to access test service, UPS should grant silent acceptance and client A should have access to //! test service.
1.818 +//! • In new session ask client B to try to access test service, UPS should grant silent denial and client B should NOT have access to //! test service.
1.819 +//!
1.820 +//! @SYMTestExpectedResults • Decision DB is upgraded with new decisions for Clients B (“never”) and
1.821 +//! A (“always”).
1.822 +//! • UPS does not malfunction after cancellation of dialog for Client C.
1.823 +//! @SYMTestType CIT
1.824 +//!
1.825 +
1.826 +
1.827 +START_TESTCASE SEC-UPS-INTEG-C007
1.828 +
1.829 +// Delete Existing Database
1.830 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.831 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.832 +
1.833 +// Client A, B and C are run concurrently with a Coordinator so that the last dialog (Client C) can be cancelled once all of the service requests
1.834 +// have been invoked
1.835 +CONCURRENT
1.836 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini cancellation_last_dialog_Coordinator
1.837 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_last_dialog_ClientA
1.838 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_last_dialog_ClientB
1.839 +RUN_TEST_STEP 100 TUPSInteg_minor CancelPrompt z:\tups\integ\scripts\tups_integ.ini cancellation_last_dialog_ClientC_cancel
1.840 +CONSECUTIVE
1.841 +
1.842 +// Database Management Checks
1.843 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini cancellation_last_dialog_dbManagementCheck
1.844 +
1.845 +END_TESTCASE SEC-UPS-INTEG-C007
1.846 +
1.847 +
1.848 +
1.849 +//! @SYMTestCaseID SEC-UPS-INTEG-C008
1.850 +//! @SYMTestCaseDesc Cancellation of middle position dialog from a queue of pending security dialogs.
1.851 +//! (cancellation_middle_dialog)
1.852 +//!
1.853 +//! @SYMPREQ PREQ1262
1.854 +//! @SYMREQ REQ7431 REQ7432
1.855 +//!
1.856 +//! @SYMTestPriority Critical
1.857 +//! @SYMTestStatus Implemented
1.858 +//! @SYMTestActions Preconditions:
1.859 +//! • For each of the services there is an appropriate policy, policy evaluator and dialog creator that matches the UID of the service //! offered by the “system server”.
1.860 +//!
1.861 +//! Test Actions:
1.862 +//! • Launch 3 “test client” in turns (A, B & C), these Clients try to use of a test service in system server.
1.863 +//! • Make sure system server has request security dialog for all clients before acting in any security dialog.
1.864 +//! • Security dialog for client A should appear on screen select “always” and check that application can use intended service.
1.865 +//! • Once user prompt is displayed for client B, induce system server to cancel request to UPS for client B, this should cause security //! dialog for client B to be removed from screen.
1.866 +//! • Security dialog for client C should appear on screen select “Always” and check that client can use intended service.
1.867 +//! • In new session ask client A to try to access test service, UPS should grant silent acceptance and client A should have access to //! test service.
1.868 +//! • In new session ask client C to try to access test service, UPS should grant silent acceptance and client B should have access to //! test service.
1.869 +//!
1.870 +//! @SYMTestExpectedResults • Decision DB is upgraded with 2 new “Always” decisions for Clients A & C.
1.871 +//! • UPS does not malfunction after cancellation of dialog for Client B.
1.872 +//!
1.873 +//! @SYMTestType CIT
1.874 +
1.875 +
1.876 +START_TESTCASE SEC-UPS-INTEG-C008
1.877 +
1.878 +// Delete Existing Database
1.879 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.880 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.881 +
1.882 +// Client A, B and C are run concurrently with a Coordinator so that the middle dialog (Client B) can be cancelled once all of the service requests
1.883 +// have been invoked
1.884 +CONCURRENT
1.885 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini cancellation_middle_dialog_Coordinator
1.886 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_middle_dialog_ClientA
1.887 +RUN_TEST_STEP 100 TUPSInteg_minor CancelPrompt z:\tups\integ\scripts\tups_integ.ini cancellation_middle_dialog_ClientB_cancel
1.888 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_middle_dialog_ClientC
1.889 +CONSECUTIVE
1.890 +
1.891 +// Database Management Checks
1.892 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini cancellation_middle_dialog_dbManagementCheck
1.893 +
1.894 +END_TESTCASE SEC-UPS-INTEG-C008
1.895 +
1.896 +
1.897 +//! @SYMTestCaseID SEC-UPS-INTEG-C009
1.898 +//! @SYMTestCaseDesc Cancellation of request whilst Policy Evaluator is Generating Fingerprints
1.899 +//! (cancellation_during_fingerprint_generation)
1.900 +//!
1.901 +//! @SYMPREQ PREQ1262
1.902 +//! @SYMREQ REQ7431 REQ7432
1.903 +//!
1.904 +//! @SYMTestPriority Critical
1.905 +//! @SYMTestStatus Implemented
1.906 +//! @SYMTestActions
1.907 +//! Preconditions:
1.908 +//! • For each of the services there is an appropriate policy, policy evaluator and
1.909 +//! dialog creator that matches the UID of the service offered by the “system server”.
1.910 +//! Test Actions:
1.911 +//! • Launch 3 “test client” in turns (A, B & C), these Clients try to use of a test
1.912 +//! service in system server.
1.913 +//! • Make sure system server has request security dialog for all clients to UPS before
1.914 +//! acting in any security dialog. At this stage client A should be hold with security
1.915 +//! dialog open (on display), client B need to be hold while its request is at
1.916 +//! “GenerateFingerPrints” stage, client C can be hold at display queuing stage.
1.917 +//! • Once all clients have reached stages described above cancel request from client B,
1.918 +//! consecutively let other two clients requests (A & C) run normally to competition.
1.919 +//! • Check that request for A and C can be served normally by UPS.
1.920 +//! • Check that request for client B received a “KerrCancel” from UPS.
1.921 +//!
1.922 +//! @SYMTestExpectedResults • Decisions for client A and C are correctly stored in decision DB.
1.923 +//! • No decision was stored for client B.
1.924 +//!
1.925 +//! @SYMTestType CIT
1.926 +
1.927 +START_TESTCASE SEC-UPS-INTEG-C009
1.928 +
1.929 +// Delete Existing Database
1.930 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.931 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.932 +
1.933 +// Client A, B and C are run concurrently with a Coordinator so that the middle dialog (Client B) can be cancelled whilst the policy evaluator is generating
1.934 +// fingerprints
1.935 +CONCURRENT
1.936 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_fingerprint_generation_Coordinator
1.937 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_fingerprint_generation_ClientA
1.938 +RUN_TEST_STEP 100 TUPSInteg_minor CancelPrompt z:\tups\integ\scripts\tups_integ.ini cancellation_during_fingerprint_generation_ClientB_cancel
1.939 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_fingerprint_generation_ClientC
1.940 +CONSECUTIVE
1.941 +
1.942 +// Database Management Checks
1.943 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_fingerprint_generation_dbManagementCheck
1.944 +
1.945 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini count_2
1.946 +
1.947 +END_TESTCASE SEC-UPS-INTEG-C009
1.948 +
1.949 +
1.950 +//! @SYMTestCaseID SEC-UPS-INTEG-C010
1.951 +//! @SYMTestCaseDesc Cancellation of request whilst Dialog Creator is Preparing a Dialog
1.952 +//! (cancellation_during_prepare_dialog)
1.953 +//!
1.954 +//! @SYMPREQ PREQ1262
1.955 +//! @SYMREQ REQ7431 REQ7432
1.956 +//!
1.957 +//! @SYMTestPriority Critical
1.958 +//! @SYMTestStatus Implemented
1.959 +//! @SYMTestActions
1.960 +//! Preconditions:
1.961 +//! • For each of the services there is an appropriate policy, policy evaluator and
1.962 +//! dialog creator that matches the UID of the service offered by the “system server”.
1.963 +//! Test Actions:
1.964 +//! • Launch 3 “test client” in turns (A, B & C), these Clients try to use of a test
1.965 +//! service in system server.
1.966 +//! • Make sure system server has request security dialog for all clients to UPS before
1.967 +//! acting in any security dialog. At this stage client A should be hold with security
1.968 +//! dialog open (on display), client B need to be hold while its request is at
1.969 +//! “PrepareDialog” stage, client C can be hold at display queuing stage.
1.970 +//! • Once all clients have reached stages described above cancel request from client B,
1.971 +//! consecutively let other two clients requests (A & C) run normally to competition.
1.972 +//! • Check that request for A and C can be served normally by UPS.
1.973 +//! • Check that request for client B received a “KerrCancel” from UPS.
1.974 +//!
1.975 +//! @SYMTestExpectedResults • Decisions for client A and C are correctly stored in decision DB.
1.976 +//! • No decision was stored for client B.
1.977 +//!
1.978 +//! @SYMTestType CIT
1.979 +
1.980 +
1.981 +
1.982 +START_TESTCASE SEC-UPS-INTEG-C010
1.983 +
1.984 +// Delete Existing Database
1.985 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.986 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.987 +
1.988 +// Client A, B and C are run concurrently with a Coordinator so that the middle dialog (Client B) can be cancelled whilst the dialog creator is preparing
1.989 +// a dialog
1.990 +CONCURRENT
1.991 +RUN_TEST_STEP 100 TUPSInteg_1 UPSCoordinatorStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_prepare_dialog_Coordinator
1.992 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_prepare_dialog_ClientA
1.993 +RUN_TEST_STEP 100 TUPSInteg_minor CancelPrompt z:\tups\integ\scripts\tups_integ.ini cancellation_during_prepare_dialog_ClientB_cancel
1.994 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_prepare_dialog_ClientC
1.995 +CONSECUTIVE
1.996 +
1.997 +// Database Management Checks
1.998 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini cancellation_during_prepare_dialog_dbManagementCheck
1.999 +
1.1000 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini count_2
1.1001 +
1.1002 +END_TESTCASE SEC-UPS-INTEG-C010
1.1003 +
1.1004 +
1.1005 +//********************** SEC-UPS-D : DECISION DATABASE SPECIFIC TESTS **********************
1.1006 +
1.1007 +
1.1008 +//! @SYMTestCaseID SEC-UPS-INTEG-D003
1.1009 +//! @SYMTestCaseDesc Deletion of decision DB after DB corruption
1.1010 +//! (BD_corruption)
1.1011 +//!
1.1012 +//! @SYMPREQ PREQ1262
1.1013 +//! @SYMREQ REQ0
1.1014 +//!
1.1015 +//! @SYMTestPriority Critical
1.1016 +//! @SYMTestStatus Implemented
1.1017 +//! @SYMTestActions Preconditions:
1.1018 +//! • For each of the services there is an appropriate policy, policy evaluator and
1.1019 +//! dialog creator that matches the UID of the service offered by the “system server”.
1.1020 +//!
1.1021 +//! Test Actions:
1.1022 +//! • Launch 2 “test client” in turns (A & B) these Clients try to use of a system server.
1.1023 +//! • System server asks for a user prompt to the UPS for each of the Clients.
1.1024 +//! • For the first 2 test clients (A & B) select “Always” option.
1.1025 +//! • Check that “test client” A & B can now use the intended service from the system server.
1.1026 +//! • Close client, system servers and UPS
1.1027 +//! • Change some bytes in decision DB file that will be interpreted as DB corruption.
1.1028 +//! • Launch again test clients A & B, as the decision DB is expected to have been deleted,
1.1029 +//! it is expected that 2 user prompts will be displayed again for A & B.
1.1030 +//! • Select “Never” for A and “always” for B.
1.1031 +//! • Check that A can access intended service and B can NOT.
1.1032 +//! @SYMTestExpectedResults • The decision DB is deleted after corruption and replaced with new one.
1.1033 +//! • A new DB is created with “”Never” decision for client A and “Always” decision for client B.
1.1034 +//! • Corruption of decision DB does not cause failure in UPS.
1.1035 +//! @SYMTestType CIT
1.1036 +
1.1037 +START_TESTCASE SEC-UPS-INTEG-D003
1.1038 +// First attempt of corruption
1.1039 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_adddecisions
1.1040 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1041 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_checkdecisions
1.1042 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1043 +// replaces database with corrupted database
1.1044 +RUN_UTILS CopyFile z:\tups\integ\corrupted_db_integ\ups_corrupted1.db c:\private\10283558\database\ups.db
1.1045 +RUN_UTILS MakeReadWrite c:\private\10283558\database\ups.db
1.1046 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_adddecisions
1.1047 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1048 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_checkdecisions
1.1049 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1050 +
1.1051 +// second attempt of corruption
1.1052 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1053 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_adddecisions
1.1054 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1055 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_checkdecisions
1.1056 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1057 +// replaces database with corrupted database
1.1058 +RUN_UTILS CopyFile z:\tups\integ\corrupted_db_integ\ups_corrupted2.db c:\private\10283558\database\ups.db
1.1059 +// The database file is deliberately left as read only (DEF122590).
1.1060 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_adddecisions
1.1061 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1062 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini BD_corruption_checkdecisions
1.1063 +END_TESTCASE SEC-UPS-INTEG-D003
1.1064 +
1.1065 +
1.1066 +//! @SYMTestCaseID SEC-UPS-D004
1.1067 +//! @SYMTestCaseDesc Removal of single decision from DB by user operation.
1.1068 +//! (remove_single_db_decision)
1.1069 +//!
1.1070 +//! @SYMPREQ PREQ1262
1.1071 +//! @SYMREQ REQ7379
1.1072 +//!
1.1073 +//! @SYMTestPriority Critical
1.1074 +//! @SYMTestStatus Implemented
1.1075 +//! @SYMTestActions Preconditions:
1.1076 +//! • For each of the services There is an appropriate policy, policy evaluator and dialog creator that matches the UID //! of the service offered by the “system server”.
1.1077 +//!
1.1078 +//! Test Actions:
1.1079 +//! • Populate decision DB for 3 test clients (A, B, C) with “Never” decisions for 3 Clients.
1.1080 +//! • Remove individual decision for Client B from DB using decision DB management API.
1.1081 +//! • Launch test clients (A, B, C) which should try to use service from system server.
1.1082 +//! • System server requests UPS for security for user security prompting, at this point UPS should give silent denial //! for Client A & C, but should prompt user security dialog for Client B.
1.1083 +//! • Select “Always” for test client B when security dialog is displayed.
1.1084 +//! • Check that Client B can now use the intended service.
1.1085 +//!
1.1086 +//! @SYMTestExpectedResults • Only decision for test client B changes; final state of decision DB should show decisions for A & C as
1.1087 +//! “never”, decision for C as “Always”.
1.1088 +//! • Test client B is granted access to intended service.
1.1089 +//!
1.1090 +//! @SYMTestType CIT
1.1091 +
1.1092 +
1.1093 +START_TESTCASE SEC-UPS-D004
1.1094 +
1.1095 +// Delete Existing Database
1.1096 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1097 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1098 +
1.1099 +// * STAGE 1 - CONSECUTIVE REMOVAL OF DECISIONS FROM DATABASE
1.1100 +
1.1101 +// Populate decisions in the database and close off sessions
1.1102 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_setup_clientA
1.1103 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_setup_clientB
1.1104 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_setup_clientC
1.1105 +
1.1106 +// Initial check on the decisions for denial from UPS
1.1107 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_initialCheck_clientA
1.1108 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_initialCheck_clientB
1.1109 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_initialCheck_clientC
1.1110 +
1.1111 +// Initial Database Management Record Check and Count
1.1112 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_initialDBCheck
1.1113 +
1.1114 +// Remove database decisions for client B using the UPS DB Management API
1.1115 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_removeDecision_clientB
1.1116 +
1.1117 +// UPS DB Management checking on records and Execute Decision Count
1.1118 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_postClientRemovalDBCheck
1.1119 +
1.1120 +// Remove database decisions for Policy Evaluator 2 using the UPS DB Management API
1.1121 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_removeDecision_evaluator2
1.1122 +
1.1123 +// UPS DB Management checking on records and Execute Decision Count
1.1124 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_postEvaluatorRemovalDBCheck
1.1125 +
1.1126 +// Relaunch clients checking that clients A & C requesting PE 1 or 3 return denials and others require a User Prompt of which
1.1127 +// Always is selected
1.1128 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_checkAndRepopulate_clientA
1.1129 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_checkAndRepopulate_clientB
1.1130 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_checkAndRepopulate_clientC
1.1131 +
1.1132 +// Final check on the decisions from UPS
1.1133 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_finalCheck_clientA
1.1134 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_finalCheck_clientB
1.1135 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_finalCheck_clientC
1.1136 +
1.1137 +// Final Stage of UPS DB Management checking on records and Execute Decision Count
1.1138 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_single_db_decision_finalDBCheck
1.1139 +
1.1140 +
1.1141 +// * STAGE 2 - CONCURRENT OPERATIONS ON UPS WHILST REMOVING DECISIONS FROM DATABASE
1.1142 +
1.1143 +// Delete Existing Database
1.1144 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1145 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1146 +
1.1147 +// populate decision database with sample inital values.
1.1148 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample
1.1149 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.1150 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.1151 +
1.1152 +// Perform initial checking on sample decisions
1.1153 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample
1.1154 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.1155 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.1156 +
1.1157 +// Concurrently check the decisions of clients B & C whilst remove select decisions from the Database for Client A
1.1158 +CONCURRENT
1.1159 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_decisions_concurrent_clientA
1.1160 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.1161 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.1162 +CONSECUTIVE
1.1163 +
1.1164 +// UPS DB Management checking on records and Execute Decision Count
1.1165 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_decisions_concurrent_dbCheck
1.1166 +
1.1167 +END_TESTCASE SEC-UPS-D004
1.1168 +
1.1169 +
1.1170 +//********************** SEC-UPS-E : SECURITY POLICIES AND POLICY EVALUATOR PLUG-INS **********************
1.1171 +//! @SYMTestCaseID SEC-UPS-INTEG-E001
1.1172 +//! @SYMTestCaseDesc To ensure that when a single bit is set in the “options” no security
1.1173 +//! dialog will be prompted to user.
1.1174 +//! (single_bit_set)
1.1175 +//!
1.1176 +//! @SYMPREQ PREQ1262
1.1177 +//! @SYMREQ REQ7391, REQ7392, REQ7433
1.1178 +//! @SYMTestPriority Critical
1.1179 +//! @SYMTestStatus Implemented
1.1180 +//! @SYMTestActions Test A: Set only ‘EYes’ bit to true in test policy for“test client”.
1.1181 +//! Induce UPS invocation by using a “test client”
1.1182 +//! Check if test client can access intended service.
1.1183 +//! Test B: Set only ‘ENo’ bit to true in test policy for“test client”.
1.1184 +//! Induce UPS invocation by using a “test client”
1.1185 +//! Check if test client can access intended service.
1.1186 +//! Test C: Set only ‘ESession’ bit to true in test policy for“test client”.
1.1187 +//! Induce UPS invocation by using a “test client”
1.1188 +//! Check if test client can access intended service.
1.1189 +//! Test D: Set only ‘EAlways’ bit to true in test policy for“test client”.
1.1190 +//! Induce UPS invocation by using a “test client”
1.1191 +//! Check if test client can access intended service.
1.1192 +//! Test E: Set only ‘ENever’ bit to true in test policy for“test client”.
1.1193 +//! Induce UPS invocation by using a “test client”
1.1194 +//! Check if test client can access intended service.
1.1195 +//!
1.1196 +//! @SYMTestExpectedResults Only for tests A, C & D the test service will be able to access
1.1197 +//! intended service.
1.1198 +//! For all of the tests (A to E), no decision is stored in decision DB.
1.1199 +//! No security dialog is displayed (all decisions are silent).
1.1200 +//!
1.1201 +//! @SYMTestType CIT
1.1202 +//
1.1203 +START_TESTCASE SEC-UPS-INTEG-E001
1.1204 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini single_bit_set
1.1205 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini single_bit_set_b
1.1206 +END_TESTCASE SEC-UPS-INTEG-E001
1.1207 +
1.1208 +
1.1209 +//! @SYMTestCaseID SEC-UPS-INTEG-E002
1.1210 +//! @SYMTestCaseDesc To ensure that a default policy evaluator will be invoked if a service
1.1211 +//! requested do not match any existing policy in the phone
1.1212 +//! (no_matching_policy)
1.1213 +//!
1.1214 +//! @SYMPREQ PREQ1262
1.1215 +//! @SYMREQ REQ0
1.1216 +//! @SYMTestPriority Critical
1.1217 +//! @SYMTestStatus Implemented
1.1218 +//! @SYMTestActions Preconditions: There is not matching policy for the test client to
1.1219 +//! be used for this test case.
1.1220 +//! Test Actions:
1.1221 +//! - Launch test client which tries to access test service, system server
1.1222 +//! should invoke UPS.
1.1223 +//! - A “Yes” or “No” dialog should be displayed select “YES
1.1224 +//! Check that access is granted to test service.
1.1225 +//! - Launch again same test client, a “Yes” or “Not” dialog should be displayed
1.1226 +//! select “No”.
1.1227 +//! - Check that access is NOT granted to test service.
1.1228 +//! - Launch again same test client, a “Yes” or “Not” dialog should be displayed
1.1229 +//! select “Yes”.
1.1230 +//! - Check that access is granted to test service.
1.1231 +//!
1.1232 +//! @SYMTestExpectedResults Yes” or “No” dialog is displayed every time that test client
1.1233 +//! request service access.
1.1234 +//!
1.1235 +//! @SYMTestType CIT
1.1236 +//
1.1237 +START_TESTCASE SEC-UPS-INTEG-E002
1.1238 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep Z:\tups\integ\scripts\tups_integ.ini no_matching_policy
1.1239 +END_TESTCASE SEC-UPS-INTEG-E002
1.1240 +
1.1241 +
1.1242 +//! @SYMTestCaseID SEC-UPS-INTEG-E004
1.1243 +//! @SYMTestCaseDesc To ensure that UPS will return an appropriate error if the policy
1.1244 +//! evaluator set in the “policy evaluator” field is not present in the phone
1.1245 +//! (missing_policy_evaluator)
1.1246 +//!
1.1247 +//! @SYMPREQ PREQ1262
1.1248 +//! @SYMREQ REQ7444
1.1249 +//! @SYMTestPriority Critical
1.1250 +//! @SYMTestStatus Implemented
1.1251 +//! @SYMTestActions Preconditions there is an appropriate policy, policy evaluator
1.1252 +//! and dialog creator that matches the UID of the service offered by the
1.1253 +//! “system server”. However the policy evaluator referred in the “policy
1.1254 +//! evaluator UID field” is not present in the phone.
1.1255 +//! Actions: Launch test client which tries to use test service, system server should invoke UPS.
1.1256 +//! UPS should return KErrUpsMissingPolicyEvaluator to system server.
1.1257 +//!
1.1258 +//! @SYMTestExpectedResults System server receives KErrUpsMissingPolicyEvaluator
1.1259 +//! and test client can not use intended service
1.1260 +//!
1.1261 +//! @SYMTestType CIT
1.1262 +//
1.1263 +START_TESTCASE SEC-UPS-INTEG-E004
1.1264 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini missing_policy_evaluator
1.1265 +END_TESTCASE SEC-UPS-INTEG-E004
1.1266 +
1.1267 +
1.1268 +//! @SYMTestCaseID SEC-UPS-INTEG-E006
1.1269 +//! @SYMTestCaseDesc To ensure that UPS will return appropriate error if dialog creator referred
1.1270 +//! by “Dialog creator UID” field in policy is not present in phone
1.1271 +//! (missing_dialog_creator)
1.1272 +//!
1.1273 +//! @SYMPREQ PREQ1262
1.1274 +//! @SYMREQ REQ7444
1.1275 +//! @SYMTestPriority Critical
1.1276 +//! @SYMTestStatus Implemented
1.1277 +//! @SYMTestActions preconditions There is an appropriate policy, policy evaluator that matches
1.1278 +//! the UID of the service offered by the “system server”. However the dialog
1.1279 +//! creator referred in the “Dialog creator UID field” is not present in the phone.
1.1280 +//! Launch test client which tries to access test service, system server should
1.1281 +//! invoke UPS. Launch test client which tries to use test service, system server
1.1282 +//! should invoke UPS.
1.1283 +//!
1.1284 +//! @SYMTestExpectedResults System server receives KErrUpsMissingDialogCreator
1.1285 +//! and test client can not use intended service
1.1286 +//!
1.1287 +//! @SYMTestType CIT
1.1288 +//
1.1289 +START_TESTCASE SEC-UPS-INTEG-E006
1.1290 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini missing_dialog_creator
1.1291 +END_TESTCASE SEC-UPS-INTEG-E006
1.1292 +
1.1293 +//! @SYMTestCaseID SEC-UPS-INTEG-E007
1.1294 +//! @SYMTestCaseDesc Matching destination by wild card, asterisk symbols – limited range.
1.1295 +//! (asterisk_limited)
1.1296 +//!
1.1297 +//! @SYMPREQ PREQ1262
1.1298 +//! @SYMREQ REQ0
1.1299 +//!
1.1300 +//! @SYMTestPriority Critical
1.1301 +//! @SYMTestStatus Implemented
1.1302 +//! @SYMTestActions Preconditions:
1.1303 +//! • There is an appropriate policy, policy evaluator and dialog creator
1.1304 +//! that matches the UID of the service offered by the “system server”.
1.1305 +//! The value for “destination” in policy file contains asterisk.
1.1306 +//! Test Actions:
1.1307 +//! • Launch test client A which tries to access test service. The service
1.1308 +//! requested by this Client is a phone connection to a 0900 number.
1.1309 +//! (The policy associated to this service states that all 0900* should be
1.1310 +//! prompted for user decision)
1.1311 +//! • System server asks for a user prompt to the UPS.
1.1312 +//! • When UPS prompts user, select the “Always” option. Check that Client
1.1313 +//! A can access intended service.
1.1314 +//! • Launch Client A in a new session, check that Client A receives a silent
1.1315 +//! acceptance and can access the intended service.
1.1316 +//! • Launch test client B which tries to access test service. The service
1.1317 +//! requested by this Client is an internet connection to a “.RU” address.
1.1318 +//! (The policy associated to this service states that all “.RU” addresses
1.1319 +//! should be blocked).
1.1320 +//! • System server asks for a user prompt to the UPS.
1.1321 +//! • UPS should reply with a silent denial. Check that Client B can not
1.1322 +//! access intended service.
1.1323 +//!
1.1324 +//! @SYMTestExpectedResults • An “Always” decision is stored in decision DB for Client A.
1.1325 +//! • Client A can access intended service.
1.1326 +//! • No decision is stored for Client B in decision DB.
1.1327 +//! • Client B can NOT access intended service.
1.1328 +//! @SYMTestType CIT
1.1329 +
1.1330 +START_TESTCASE SEC-UPS-INTEG-E007
1.1331 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini asterisk_limited
1.1332 +END_TESTCASE SEC-UPS-INTEG-E007
1.1333 +
1.1334 +
1.1335 +//! @SYMTestCaseID SEC-UPS-INTEG-E008
1.1336 +//! @SYMTestCaseDesc Matching destination by wild card, asterisk symbols – All option.
1.1337 +//! (asterisk_all)
1.1338 +//!
1.1339 +//! @SYMPREQ PREQ1262
1.1340 +//! @SYMREQ REQ0
1.1341 +//!
1.1342 +//! @SYMTestPriority Critical
1.1343 +//! @SYMTestStatus Implemented
1.1344 +//! @SYMTestActions Preconditions:
1.1345 +//! • There is an appropriate policy, policy evaluator and dialog creator
1.1346 +//! that matches the UID of the service offered by the “system server”.
1.1347 +//! The value for “destination” in policy file contains asterisk.
1.1348 +//! Test Actions:
1.1349 +//! • Launch test client A with which tries to access test service.
1.1350 +//! The service requested by this Client is a phone connection to a 0500 number.
1.1351 +//! (The policy associated to this service states that all destinations should be prompted
1.1352 +//! for user decision, “*” in destination)
1.1353 +//! • System server asks for a user prompt to the UPS.
1.1354 +//! • When UPS prompts user, select the “Always” option. Check that Client A can
1.1355 +//! access intended service.
1.1356 +//! • Launch Client A in a new session, check that Client A receives a silent acceptance
1.1357 +//! and can access the intended service.
1.1358 +//! • Launch test client B which tries to access test service. The service requested by this
1.1359 +//! Client is an internet connection to a “.RU” address. (The policy associated to this service
1.1360 +//! states that all “.RU” addresses should be blocked).
1.1361 +//! • System server asks for a user prompt to the UPS.
1.1362 +//! • UPS should reply with a silent denial. Check that Client B can not access intended service.
1.1363 +//!
1.1364 +//!
1.1365 +//! @SYMTestExpectedResults • An “Always” decision is stored in decision DB for Client A.
1.1366 +//! • Client A can access intended service.
1.1367 +//! • No decision is stored for Client B in decision DB.
1.1368 +//! • Client B can NOT access intended service.
1.1369 +//! @SYMTestType CIT
1.1370 +
1.1371 +START_TESTCASE SEC-UPS-INTEG-E008
1.1372 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini asterisk_all
1.1373 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini asterisk_all_b
1.1374 +END_TESTCASE SEC-UPS-INTEG-E008
1.1375 +
1.1376 +
1.1377 +//! @SYMTestCaseID SEC-UPS-INTEG-E009
1.1378 +//! @SYMTestCaseDesc Matching destination by wild card, question mark symbols.
1.1379 +//! (question_mark_card)
1.1380 +//!
1.1381 +//! @SYMPREQ PREQ1262
1.1382 +//! @SYMREQ REQ0
1.1383 +//!
1.1384 +//! @SYMTestPriority Critical
1.1385 +//! @SYMTestStatus Implemented
1.1386 +//! @SYMTestActions Preconditions:
1.1387 +//! • There is an appropriate policy, policy evaluator and dialog creator that
1.1388 +//! matches the UID of the service offered by the “system server”. The value
1.1389 +//! for “destination” in policy file contains question mark symbols.
1.1390 +//! Test Actions:
1.1391 +//! • Launch test client A which tries to access test service. The service requested
1.1392 +//! by this Client is a phone connection to a 0900 number. (The policy associated to
1.1393 +//! this service states that all 0?00 should be prompted for user decision)
1.1394 +//! • System server asks for a user prompt to the UPS.
1.1395 +//! • When UPS prompts user, select the “Always” option. Check that Client A can access
1.1396 +//! intended service.
1.1397 +//! • Launch Client A in a new session, check that Client A receives a silent acceptance
1.1398 +//! and can access the intended service.
1.1399 +//! • Launch test client B which tries to access test service. The service requested by
1.1400 +//! this Client is an phone call to 118 500. (The policy associated to this service states
1.1401 +//! that all 118??? Phone numbers should be blocked).
1.1402 +//! • System server asks for a user prompt to the UPS.
1.1403 +//! • UPS should reply with a silent denial. Check that Client B can not access intended
1.1404 +//! service.
1.1405 +//!
1.1406 +//!
1.1407 +//! @SYMTestExpectedResults • An “Always” decision is stored in decision DB for Client A.
1.1408 +//! • Client A can access intended service.
1.1409 +//! • No decision is stored for Client B in decision DB.
1.1410 +//! • Client B can NOT access intended service.
1.1411 +//! @SYMTestType CIT
1.1412 +
1.1413 +START_TESTCASE SEC-UPS-INTEG-E009
1.1414 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini question_mark_card
1.1415 +END_TESTCASE SEC-UPS-INTEG-E009
1.1416 +
1.1417 +
1.1418 +//! @SYMTestCaseID SEC-INTEG-UPS-E024
1.1419 +//! @SYMTestCaseDesc Security Policy Authorisation - EAlwaysCheck
1.1420 +//! (alwayscheck_authoristion)
1.1421 +//!
1.1422 +//! @SYMPREQ PREQ1262
1.1423 +//! @SYMREQ REQ7389
1.1424 +//! @SYMTestPriority Critical
1.1425 +//! @SYMTestStatus Implemented
1.1426 +//! @SYMTestActions
1.1427 +//! Preconditions:
1.1428 +//! • Policy file related to test service to be used has property “authorisationPolicy” set
1.1429 +//! to “EAlwaysCheck”.
1.1430 +//! Test Actions:
1.1431 +//! • Request use of the service that matches policy file mentioned in “preconditions”.
1.1432 +//! Test system server should invoke UPS.
1.1433 +//! • Use different values for “aServerCheckOk” parameter in “Authorise” methods (ETrue
1.1434 +//! and EFalse)
1.1435 +//! • Check that UPS invokes correct policy evaluator and dialog creator as set in policy
1.1436 +//! file.
1.1437 +//!
1.1438 +//! @SYMTestExpectedResults
1.1439 +//! • All new requests made to UPS for test service will cause a user prompt from UPS.
1.1440 +//!
1.1441 +//! @SYMTestType CIT
1.1442 +
1.1443 +START_TESTCASE SEC-INTEG-UPS-E024
1.1444 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini alwayscheck_platsec_true
1.1445 +
1.1446 +// Delete Existing Database
1.1447 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1448 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1449 +
1.1450 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini alwayscheck_platsec_false
1.1451 +END_TESTCASE SEC-INTEG-UPS-E024
1.1452 +
1.1453 +
1.1454 +//! @SYMTestCaseID SEC-INTEG-UPS-E025
1.1455 +//! @SYMTestCaseDesc Security Policy Authorisation - ECheckPostManufacture
1.1456 +//! (checkpostmanufacture_authoristion)
1.1457 +//!
1.1458 +//! @SYMPREQ PREQ1262
1.1459 +//! @SYMREQ REQ7389
1.1460 +//! @SYMTestPriority Critical
1.1461 +//! @SYMTestStatus Implemented
1.1462 +//! @SYMTestActions Preconditions:
1.1463 +//! • Policy file related to test service to be used has property “authorisationPolicy”
1.1464 +//! set to “ECheckPostManufacture”.
1.1465 +//! Test Actions:
1.1466 +//! • Request use of the service that matches policy file mentioned in “preconditions”.
1.1467 +//! Test system server should invoke UPS.
1.1468 +//! • Use different values for “aServerCheckOk” parameter in “Authorise” methods (ETrue
1.1469 +//! and EFalse).
1.1470 +//! • Use different types of applications to request the same service including: applications
1.1471 +//! with protected SID on Z drive, unprotected SID on Z drive, protected SID on C drive and
1.1472 +//! unprotected SID on C drive.
1.1473 +//!
1.1474 +//! @SYMTestExpectedResults Only requests made from applications with protected SID running from Z drive having
1.1475 +//! passed system server checks should receive immediate access approval, any other type
1.1476 +//! should cause a security user prompt.
1.1477 +//!
1.1478 +//! @SYMTestType CIT
1.1479 +
1.1480 +START_TESTCASE SEC-INTEG-UPS-E025
1.1481 +
1.1482 +// Delete Existing Database
1.1483 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1484 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1485 +
1.1486 +// CLIENT WITH PROTECTED SID ON Z
1.1487 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_true_zdrive_protect
1.1488 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_false_zdrive_protect
1.1489 +
1.1490 +
1.1491 +// CLIENT WITH UNPROTECTED SID ON Z
1.1492 +RUN_TEST_STEP 100 TUPSInteg_unprotected UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_true_zdrive_unprotect
1.1493 +RUN_TEST_STEP 100 TUPSInteg_unprotected UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_false_zdrive_unprotect
1.1494 +
1.1495 +
1.1496 +// CLIENT WITH PROTECTED SID ON C
1.1497 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_true_cdrive_protect
1.1498 +
1.1499 +// Delete Existing Database
1.1500 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1501 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1502 +
1.1503 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_false_cdrive_protect
1.1504 +
1.1505 +
1.1506 +// CLIENT WITH UNPROTECTED SID ON C
1.1507 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_true_cdrive_unprotect
1.1508 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkpostmanufacture_platsec_false_cdrive_unprotect
1.1509 +
1.1510 +END_TESTCASE SEC-INTEG-UPS-E025
1.1511 +
1.1512 +
1.1513 +//! @SYMTestCaseID SEC-INTEG-UPS-E026
1.1514 +//! @SYMTestCaseDesc Security Policy Authorisation - ECheckUnprotectedSids
1.1515 +//! (checkunprotectedsids_authoristion)
1.1516 +//!
1.1517 +//! @SYMPREQ PREQ1262
1.1518 +//! @SYMREQ REQ7389
1.1519 +//! @SYMTestPriority Critical
1.1520 +//! @SYMTestStatus Implemented
1.1521 +//! @SYMTestActions
1.1522 +//! Preconditions:
1.1523 +//! • Policy file related to test service to be used has property “authorisationPolicy”
1.1524 +//! set to “ECheckUnprotectedSids”.
1.1525 +//! Test Actions:
1.1526 +//! • Request use of the service that matches policy file mentioned in “preconditions”.
1.1527 +//! Test system server should invoke UPS.
1.1528 +//! • Use different values for “aServerCheckOk” parameter in “Authorise” methods (ETrue
1.1529 +//! and EFalse).
1.1530 +//! • Use different types of applications to request the same service including:
1.1531 +//! applications with protected SID on Z drive, unprotected SID on Z drive, protected
1.1532 +//! SID on C drive and unprotected SID on C drive.
1.1533 +//!
1.1534 +//! @SYMTestExpectedResults
1.1535 +//! • Any request for tests services made from clients with protected SID should receive
1.1536 +//! immediate silent approval from UPS.
1.1537 +//! • Request for tests services made from clients with unprotected SID should cause user
1.1538 +//! security dialog from UPS.
1.1539 +//!
1.1540 +//! @SYMTestType CIT
1.1541 +
1.1542 +START_TESTCASE SEC-INTEG-UPS-E026
1.1543 +
1.1544 +// Delete Existing Database
1.1545 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1546 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1547 +
1.1548 +// CLIENT WITH PROTECTED SID ON Z
1.1549 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_true_zdrive_protect
1.1550 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_false_zdrive_protect
1.1551 +
1.1552 +// CLIENT WITH UNPROTECTED SID ON Z
1.1553 +RUN_TEST_STEP 100 TUPSInteg_unprotected UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_true_zdrive_unprotect
1.1554 +RUN_TEST_STEP 100 TUPSInteg_unprotected UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_false_zdrive_unprotect
1.1555 +
1.1556 +// CLIENT WITH PROTECTED SID ON C
1.1557 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_true_cdrive_protect
1.1558 +RUN_TEST_STEP 100 TUPSInteg_4 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_false_cdrive_protect
1.1559 +
1.1560 +// CLIENT WITH UNPROTECTED SID ON C
1.1561 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_true_cdrive_unprotect
1.1562 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkunprotectedsids_platsec_false_cdrive_unprotect
1.1563 +
1.1564 +END_TESTCASE SEC-INTEG-UPS-E026
1.1565 +
1.1566 +
1.1567 +//! @SYMTestCaseID SEC-INTEG-UPS-E027
1.1568 +//! @SYMTestCaseDesc Security Policy Authorisation - ECheckIfFailed
1.1569 +//! (checkiffailed_authoristion)
1.1570 +//!
1.1571 +//! @SYMPREQ PREQ1262
1.1572 +//! @SYMREQ REQ7389
1.1573 +//! @SYMTestPriority Critical
1.1574 +//! @SYMTestStatus Implemented
1.1575 +//! @SYMTestActions
1.1576 +//! Preconditions:
1.1577 +//! • Policy file related to test service to be used has property
1.1578 +//! “authorisationPolicy” set to “ECheckIfFailed”.
1.1579 +//! Test Actions:
1.1580 +//! • Request use of the service that matches policy file mentioned in
1.1581 +//! “preconditions”. Test system server should invoke UPS.
1.1582 +//! • Use different values for “aServerCheckOk” parameter in “Authorise”
1.1583 +//! request (ETrue and EFalse).
1.1584 +//! @SYMTestExpectedResults
1.1585 +//! • Only requests made with “aServerCheckOk” parameter set to Efalse should cause
1.1586 +//! UPS to display user security dialog, otherwise UPS should return silent approval.
1.1587 +//!
1.1588 +//! @SYMTestType CIT
1.1589 +
1.1590 +START_TESTCASE SEC-INTEG-UPS-E027
1.1591 +
1.1592 +// Delete Existing Database
1.1593 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1594 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1595 +
1.1596 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkiffailed_platsec_true
1.1597 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini checkiffailed_platsec_false
1.1598 +END_TESTCASE SEC-INTEG-UPS-E027
1.1599 +
1.1600 +
1.1601 +//! @SYMTestCaseID SEC-INTEG-UPS-E028
1.1602 +//! @SYMTestCaseDesc Security Policy Authorisation - ENeverCheck
1.1603 +//! (nevercheck_authoristion)
1.1604 +//!
1.1605 +//! @SYMPREQ PREQ1262
1.1606 +//! @SYMREQ REQ7389
1.1607 +//! @SYMTestPriority Critical
1.1608 +//! @SYMTestStatus Implemented
1.1609 +//! @SYMTestActions
1.1610 +//! Preconditions:
1.1611 +//! • Policy file related to test service to be used has property “authorisationPolicy” set
1.1612 +//! to “ENeverCheck”.
1.1613 +//! Test Actions:
1.1614 +//! • Request use of the service that matches policy file mentioned in “preconditions”. Test
1.1615 +//! system server should invoke UPS.
1.1616 +//! • Use different values for “aServerCheckOk” parameter in “Authorise” request (ETrue and
1.1617 +//! EFalse).
1.1618 +//!
1.1619 +//! @SYMTestExpectedResults
1.1620 +//! • UPS shouldn’t display any security dialog, UPS should return silent acceptance server
1.1621 +//! checks passed, UPS should return silent denial server checks failed.
1.1622 +//!
1.1623 +//! @SYMTestType CIT
1.1624 +
1.1625 +START_TESTCASE SEC-INTEG-UPS-E028
1.1626 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini nevercheck_platsec_true
1.1627 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini nevercheck_platsec_false
1.1628 +END_TESTCASE SEC-INTEG-UPS-E028
1.1629 +
1.1630 +
1.1631 +//! @SYMTestCaseID SEC-INTEG-UPS-E029
1.1632 +//! @SYMTestCaseDesc System server with no policy files
1.1633 +//! (no_policy_files_server)
1.1634 +//!
1.1635 +//! @SYMPREQ PREQ1262
1.1636 +//! @SYMREQ REQ7427
1.1637 +//!
1.1638 +//! @SYMTestPriority Critical
1.1639 +//! @SYMTestStatus Implemented
1.1640 +//! @SYMTestActions Preconditions:
1.1641 +//! • There is NO policy file at all related to the system server been used for test purpose
1.1642 +//!
1.1643 +//! Test Actions:
1.1644 +//! • Launch “test clients” which tries to use of system servers. System server should request UPS for
1.1645 +//! user security dialog. Set plat sec check to ETrue in request to UPS.
1.1646 +//! • Launch “test clients” which tries to use of system servers. System server should request UPS for
1.1647 +//! user security dialog. Set plat sec check to EFalse in request to UPS.
1.1648 +//!
1.1649 +//! @SYMTestExpectedResults • System server shuold receive a EDecisionYes for first request
1.1650 +//! • System server shuold receive a EDecisionNo for second request
1.1651 +//!
1.1652 +//! @SYMTestType CIT
1.1653 +
1.1654 +START_TESTCASE SEC-INTEG-UPS-E029
1.1655 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini no_policy_files_server
1.1656 +END_TESTCASE SEC-INTEG-UPS-E029
1.1657 +
1.1658 +
1.1659 +//! @SYMTestCaseID SEC-INTEG-UPS-E030
1.1660 +//! @SYMTestCaseDesc Option session returned for always decision stored.
1.1661 +//! (session_overwrites_always)
1.1662 +//!
1.1663 +//!
1.1664 +//! @SYMTestPurpose To check that if a policy includes the “session” option for an “always” decision already stored,
1.1665 +//! then UPS will reply with “ESession” every time this decision is queried
1.1666 +//!
1.1667 +//! @SYMPREQ
1.1668 +//!
1.1669 +//! @SYMTestPriority Critical
1.1670 +//! @SYMTestStatus Implemented
1.1671 +//! @SYMTestActions Preconditions:
1.1672 +//! • The UPS policy stated for the test service to be used allows at least the options “ESession”
1.1673 +//! and “EAlways”
1.1674 +//!
1.1675 +//! Test Actions:
1.1676 +//! • Launch “test client” which tries to connect to a system server and use service.
1.1677 +//! • System server asks for a user prompt to the UPS.
1.1678 +//! • When UPS prompts user, select the “Always” option.
1.1679 +//! • Check that UPS returned “ESession” to system server.
1.1680 +//! • In a new session request the same service and destination, check that UPS returns an “ESession”
1.1681 +//! silent reply to system server. Check that the correct policy evaluator was invoked but no dialog
1.1682 +//! creator was invoked.
1.1683 +//!
1.1684 +//!
1.1685 +//! @SYMTestExpectedResults • UPS returns “ESession” even if an “Always” decision was selected by the use.
1.1686 +//! • A new “Always” decision was added to decision DB.
1.1687 +//!
1.1688 +//! @SYMTestType CIT
1.1689 +
1.1690 +START_TESTCASE SEC-INTEG-UPS-E030
1.1691 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini session_overwrites_always
1.1692 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini session_overwrites_always_b
1.1693 +END_TESTCASE SEC-INTEG-UPS-E030
1.1694 +
1.1695 +
1.1696 +//! @SYMTestCaseID SEC-UPS-E031
1.1697 +//! @SYMTestCaseDesc To check that UPS can handle client entities of a max length of 32 bytes
1.1698 +//! (client_entity)
1.1699 +//!
1.1700 +//! @SYMPREQ PREQ1262
1.1701 +//! @SYMREQ REQ7374
1.1702 +//!
1.1703 +//! @SYMTestPriority Critical
1.1704 +//! @SYMTestStatus Implemented
1.1705 +//! @SYMTestActions Preconditions:
1.1706 +//! • Policy evaluator used for test can populate “CClientEntity” object at will.
1.1707 +//! • Appropriate policy file, policy evaluator and dialog creator are present in phone for test service
1.1708 +//! to be requested
1.1709 +//!
1.1710 +//! Test Actions:
1.1711 +//! • Make request to ups for security user prompt for some arbitrary destinations. For these destination
1.1712 +//! instruct policy evaluator to create different CClientEntity lengths including:
1.1713 +//! - 0 bytes.
1.1714 +//! - 1 bytes.
1.1715 +//! - 32 bytes.
1.1716 +//! - 33 bytes.
1.1717 +//!
1.1718 +//! • For the previous requests select “Always” or “Never” when security dialog is displayed.
1.1719 +//!
1.1720 +//! @SYMTestExpectedResults • For client entities of length 0, 1 or 32 bytes a corresponding decision is expected to be
1.1721 +//! created in decision database. The client entity value is reported correctly in DB.
1.1722 +//!
1.1723 +//! • For CClientEntity of 33 bytes length, the constructor is expected to return
1.1724 +//! KErrUpsBadClientEntityLength and no decision is created in database.
1.1725 +//!
1.1726 +//! @SYMTestType CIT
1.1727 +
1.1728 +START_TESTCASE SEC-UPS-E031
1.1729 +
1.1730 +// Delete Existing Database
1.1731 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1732 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1733 +
1.1734 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini client_Entity
1.1735 +
1.1736 +END_TESTCASE SEC-UPS-E031
1.1737 +
1.1738 +
1.1739 +//! @SYMTestCaseID SEC-UPS-E032
1.1740 +//! @SYMTestCaseDesc Force prompt – decision removed
1.1741 +//! (force_prompt_decision_removed)
1.1742 +//!
1.1743 +//! @SYMPREQ PREQ1262
1.1744 +//! @SYMREQ REQ0
1.1745 +//!
1.1746 +//! @SYMTestPriority Critical
1.1747 +//! @SYMTestStatus Implemented
1.1748 +//! @SYMTestActions Preconditions:
1.1749 +//! • There is an appropriate policy file for the test service to be use.
1.1750 +//! • Policy evaluator has the ability to force prompt at run time. Policy evaluator increases by
1.1751 +//! one the value of “evaluator info” every time that a security dialog is prompted for a particular
1.1752 +//! decision in the DB.
1.1753 +//!
1.1754 +//! Test Actions:
1.1755 +//! • Part 1: Test client A has two pre-stored decision as “Always”.
1.1756 +//! • Instruct client A to request access to test service that matches its pre-stored decisions,
1.1757 +//! instruct policy evaluator to force prompt new security dialog for these decisions.
1.1758 +//! • When new security dialogs appear select “yes” for one of the pre-stored decisions and select
1.1759 +//! “no” for the other decision”.
1.1760 +//! • Check that both pre-stored decision for client A were removed from DB.
1.1761 +//!
1.1762 +//! • Part 2: Test client B has two pre-stored decision as “Never”.
1.1763 +//! • Instruct client B to request access to test service that matches its pre-stored decisions,
1.1764 +//! instruct policy evaluator to force prompt new security dialog for these decisions.
1.1765 +//! • When new security dialogs appear select “yes” for one of the pre-stored decisions and select
1.1766 +//! “no” for the other decision”.
1.1767 +//! • Check that both pre-stored decision for client B were removed from DB.
1.1768 +//!
1.1769 +//! @SYMTestExpectedResults • Decisions in database where updated correctly in DB.
1.1770 +//! • “client info” field was increased by two at the end of test.
1.1771 +//!
1.1772 +//! @SYMTestType CIT
1.1773 +
1.1774 +
1.1775 +START_TESTCASE SEC-UPS-E032
1.1776 +
1.1777 +//* PART 1
1.1778 +
1.1779 +// Delete Existing Database
1.1780 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1781 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1782 +
1.1783 +// Client A setup of pre-stored decisions
1.1784 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientA_setup
1.1785 +
1.1786 +// Initial check to ensure that DB decision acceptance is issued by UPS
1.1787 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientA_initialCheck
1.1788 +
1.1789 +// Check decision database state before force prompting
1.1790 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientA_intitalDbCheck
1.1791 +
1.1792 +// Force the dialog prompt on the Decisions stored about Client A in the Database
1.1793 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientA_forcePrompt
1.1794 +
1.1795 +// Check that decisions have been removed and that new options can be chosen
1.1796 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientA_noDecisionCheck
1.1797 +
1.1798 +// Check for No Decisions using Database Management Step
1.1799 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientA_dbManagementCheck
1.1800 +
1.1801 +
1.1802 +// * PART 2
1.1803 +
1.1804 +// Client B setup of pre-stored decisions
1.1805 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientB_setup
1.1806 +
1.1807 +// Initial check to ensure that DB decision denial is issued by UPS
1.1808 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientB_initialCheck
1.1809 +
1.1810 +// Check decision database state before force prompting
1.1811 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientB_intitalDbCheck
1.1812 +
1.1813 +// Force the dialog prompt on the Decisions stored about Client B in the Database
1.1814 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientB_forcePrompt
1.1815 +
1.1816 +// Check that decisions have been removed and that new options can be chosen
1.1817 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientB_noDecisionCheck
1.1818 +
1.1819 +// Check for No Decisions using Database Management Step
1.1820 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_decision_removed_clientB_dbManagementCheck
1.1821 +
1.1822 +END_TESTCASE SEC-UPS-E032
1.1823 +
1.1824 +
1.1825 +//**************************************************************************************************************
1.1826 +
1.1827 +
1.1828 +//! @SYMTestCaseID SEC-UPS-E033
1.1829 +//! @SYMTestCaseDesc Force prompt – multiple fingerprints- record overwritten
1.1830 +//! (force_prompt_multifingerprint_overwriterecord)
1.1831 +//!
1.1832 +//! @SYMPREQ PREQ1262
1.1833 +//! @SYMREQ REQ7409 REQ7403
1.1834 +//!
1.1835 +//! @SYMTestPriority Critical
1.1836 +//! @SYMTestStatus Implemented
1.1837 +//! @SYMTestActions Preconditions:
1.1838 +//! • There is an appropriate policy file for the test service to be use.
1.1839 +//! • Policy evaluator has the ability to force prompt at run time. Policy evaluator increases by one
1.1840 +//! the value of “evaluator info” every time that a security dialog is prompted for a particular
1.1841 +//! decision in the DB.
1.1842 +//! • Policy evaluator generates 3 fingerprints FP1, FP2 & FP3 which are checked by UPS in decision DB
1.1843 +//! in that order (FP1 would be the first match if all 3 fingerprints exist in decision DB.
1.1844 +//!
1.1845 +//! Test Actions:
1.1846 +//! • Part 1: Test client A has 3 pre-stored decision as “Always” matching FP1, FP2 & FP3.
1.1847 +//! • Instruct client A to request access to test service that matches FP1. Test system server should
1.1848 +//! invoke UPS for decision check. When policy evaluator is invoked instruct this one to generate FP1,
1.1849 +//! FP2 & FP3.
1.1850 +//! • At dialog display stage select “never” for fingerprint FP3.
1.1851 +//! • Check that finger print FP1 was removed from DB, FP2 remain unchanged, FP3 was replaced with a
1.1852 +//! Never Decision
1.1853 +//! • “Evaluator info is increased by 1.
1.1854 +//!
1.1855 +//! • Part 2: Reset test so it remains in original conditions (3 “always” decisions for FP1, FP2 & FP3
1.1856 +//! in decision DB).
1.1857 +//! • Instruct client A to request access to test service that matches FP1. Test system server should
1.1858 +//! invoke UPS for decision check. When policy evaluator is invoked instruct this one to generate FP1,
1.1859 +//! FP2 &FP3.
1.1860 +//! • At dialog display stage select “always” for fingerprint FP3.
1.1861 +//! • Check that finger print FP1 was removed from DB, FP2 & FP3 remain unchanged.
1.1862 +//! • “Evaluator info is increased by 1.
1.1863 +//!
1.1864 +//! @SYMTestExpectedResults • First matching fingerprint FP1 is deleted from DB as this one is not selected by user in
1.1865 +//! dialog creator stage.
1.1866 +//! • FP3 is replaced with a “never” decision in case 1 but remains unchanged for case 2
1.1867 +//! (“always” decision)
1.1868 +//! • Evaluator info is increased by one in both cases.
1.1869 +//!
1.1870 +//! @SYMTestType CIT
1.1871 +
1.1872 +
1.1873 +START_TESTCASE SEC-UPS-E033
1.1874 +
1.1875 +// Delete Existing Database
1.1876 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1877 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1878 +
1.1879 +//* PART 1
1.1880 +
1.1881 +// Client setup of pre-stored 'ALWAYS' decisions using the 3 different fingerprints
1.1882 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_setup
1.1883 +
1.1884 +// Initial check to ensure that DB decisions stored for the 3 fingerprints return the expected result
1.1885 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_initialCheck
1.1886 +
1.1887 +// Check decision database state before force prompting
1.1888 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_initialDbCheck
1.1889 +
1.1890 +// Force the dialog prompt on decision FingerPrint 1, and 'NEVER' decision selected for FingerPrint 3 chosen at Dialog
1.1891 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_forcePrompt_part1
1.1892 +
1.1893 +// Check that decisions within DB have been altered/removed/added as necessary using Database Management Step
1.1894 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_dbManagementCheck_part1
1.1895 +
1.1896 +// Delete Existing Database
1.1897 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1898 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1899 +
1.1900 +
1.1901 +//* PART 2
1.1902 +
1.1903 +// Client setup of pre-stored 'ALWAYS' decisions using the 3 different fingerprints
1.1904 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_setup
1.1905 +
1.1906 +// Initial check to ensure that DB decisions stored for the 3 fingerprints return the expected result
1.1907 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_initialCheck
1.1908 +
1.1909 +// Check decision database state before force prompting
1.1910 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_initialDbCheck
1.1911 +
1.1912 +// Force the dialog prompt on decision FingerPrint 1, and 'ALWAYS' decision selected for FingerPrint 3 chosen at Dialog
1.1913 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_forcePrompt_part2
1.1914 +
1.1915 +// Check that decisions within DB have been altered/removed/added as necessary using the Database Management Step
1.1916 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_overwriterecord_dbManagementCheck_part2
1.1917 +
1.1918 +END_TESTCASE SEC-UPS-E033
1.1919 +
1.1920 +
1.1921 +//! @SYMTestCaseID SEC-UPS-E034
1.1922 +//! @SYMTestCaseDesc Force prompt – multiple fingerprints - new record
1.1923 +//! (force_prompt_multifingerprint_newrecord)
1.1924 +//!
1.1925 +//! @SYMPREQ PREQ1262
1.1926 +//! @SYMREQ REQ7409 REQ7403
1.1927 +//!
1.1928 +//! @SYMTestPriority Critical
1.1929 +//! @SYMTestStatus Implemented
1.1930 +//! @SYMTestActions Preconditions:
1.1931 +//! • There is an appropriate policy file for the test service to be use.
1.1932 +//! • Policy evaluator has the ability to force prompt at run time. Policy evaluator increases by one
1.1933 +//! the value of “evaluator info” every time that a security dialog is prompted for a particular
1.1934 +//! decision in the DB.
1.1935 +//! • Policy evaluator generates 3 fingerprints FP1, FP2 & FP3 which are checked by UPS in decision DB
1.1936 +//! in that order (FP1 would be the first match if all 3 fingerprints exist in decision DB.
1.1937 +//!
1.1938 +//! Test Actions:
1.1939 +//! • Part 1: Test client A has 2 pre-stored decision as “Always” matching FP1 & FP2.
1.1940 +//! • Instruct client A to request access to test service that matches FP1. Test system server should
1.1941 +//! invoke UPS for decision check. When policy evaluator is invoked instruct this one to generate FP1,
1.1942 +//! FP2 &FP3.
1.1943 +//! • At dialog display stage select “never” for fingerprint FP3.
1.1944 +//! • Check that finger print FP1 was removed from DB, FP2 remain unchanged, new FP3 is created in
1.1945 +//! decision DB (with never decision).
1.1946 +//! • “Evaluator info is increased by 1.
1.1947 +//!
1.1948 +//! • Part 2: Reset test so it remains in original conditions (2 “always” decisions for FP1& FP2).
1.1949 +//! • Instruct client A to request access to test service that matches FP1. Test system server should
1.1950 +//! invoke UPS for decision check. When policy evaluator is invoked instruct this one to generate FP1,
1.1951 +//! FP2 &FP3.
1.1952 +//! • At dialog display stage select “always” for fingerprint FP3.
1.1953 +//! • Check that finger print FP1 was removed from DB, FP2 remain unchanged, new FP3 is created in
1.1954 +//! decision DB (with always decision).
1.1955 +//! • “Evaluator info is increased by 1.
1.1956 +//!
1.1957 +//! @SYMTestExpectedResults • In both cases decision related to FP1 are removed from DB.
1.1958 +//! • FP3 is created with a “never” decision in case 1 and with an “always” in cases 2.
1.1959 +//! • Evaluator info is increased by one in both cases.
1.1960 +//!
1.1961 +//!
1.1962 +//! @SYMTestType CIT
1.1963 +
1.1964 +
1.1965 +START_TESTCASE SEC-UPS-E034
1.1966 +
1.1967 +// Delete Existing Database
1.1968 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1969 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1970 +
1.1971 +//* PART 1
1.1972 +
1.1973 +// Client setup of pre-stored 'ALWAYS' decisions using 2 of the 3 fingerprints
1.1974 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_setup
1.1975 +
1.1976 +// Initial check to ensure that DB decisions stored for the 2 fingerprints return the expected result
1.1977 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_initialCheck
1.1978 +
1.1979 +// Check decision database state before force prompting
1.1980 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_intitalDbCheck
1.1981 +
1.1982 +// Force the dialog prompt on decision FingerPrint 1, and 'NEVER' decision selected for FingerPrint 3 chosen at Dialog
1.1983 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_forcePrompt_part1
1.1984 +
1.1985 +// Check that decisions within DB have been altered/removed/added as necessary using the Database Management Step
1.1986 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_dbManagementCheck_part1
1.1987 +
1.1988 +// Delete Existing Database
1.1989 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.1990 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.1991 +
1.1992 +
1.1993 +//* PART 2
1.1994 +
1.1995 +// Client setup of pre-stored 'ALWAYS' decisions using 2 of the 3 fingerprints
1.1996 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_setup
1.1997 +
1.1998 +// Initial check to ensure that DB decisions stored for the 2 fingerprints return the expected result
1.1999 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_initialCheck
1.2000 +
1.2001 +// Check decision database state before force prompting
1.2002 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_intitalDbCheck
1.2003 +
1.2004 +// Force the dialog prompt on decision FingerPrint 1, and 'ALWAYS' decision selected for FingerPrint 3 chosen at Dialog
1.2005 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_forcePrompt_part2
1.2006 +
1.2007 +// Check that decisions within DB have been altered/removed/added as necessary using the Database Management Step
1.2008 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini force_prompt_multifingerprint_newrecord_dbManagementCheck_part2
1.2009 +
1.2010 +
1.2011 +END_TESTCASE SEC-UPS-E034
1.2012 +
1.2013 +
1.2014 +//! @SYMTestCaseID SEC-UPS-E035
1.2015 +//! @SYMTestCaseDesc Invocation of Default Symbian policy evaluator
1.2016 +//! (invoke_default_policy_evaluator)
1.2017 +//!
1.2018 +//! @SYMPREQ PREQ1262
1.2019 +//! @SYMREQ
1.2020 +//!
1.2021 +//! @SYMTestPriority Critical
1.2022 +//! @SYMTestStatus Implemented
1.2023 +//! @SYMTestActions
1.2024 +//!
1.2025 +//! @SYMTestExpectedResults Preconditions:
1.2026 +//! • There is an appropriate policy file for the test service to be use, but in the header of
1.2027 +//! the policy file there is NO mention of policy evaluator.
1.2028 +//! • Note: It is expected that the Symbian policy evaluator will generate a NULL value
1.2029 +//! fingerprint.
1.2030 +//! • Dialog creator specified by policy evaluator is present.
1.2031 +//!
1.2032 +//! Test Actions:
1.2033 +//! • Case 1: Request service to test system server, this one is expected to invoke UPS.
1.2034 +//! • Check that Symbian default policy evaluator was invoked.
1.2035 +//! • When security dialog is invoked select “Always”.
1.2036 +//! • Check that decision is stored correctly.
1.2037 +//!
1.2038 +//! • Case 2: Request service to test system server, this one is expected to invoke UPS.
1.2039 +//! • Check that Symbian default policy evaluator was invoked.
1.2040 +//! • When security dialog is invoked select “never”.
1.2041 +//! • Check that decision is stored correctly.
1.2042 +//!
1.2043 +//! • Extra Checking: Use dumpupsdb.exe tool to export and re-import UPS database, check
1.2044 +//! consistency of imported database.
1.2045 +//!
1.2046 +//! @SYMTestExpectedResults • Two new decisions where created: 1 “never” and 1 ”always” which are expected to have NULL
1.2047 +//! value fingerprints.
1.2048 +//! • Decision database with null value fingerprint can be exported and re-imported correctly.
1.2049 +//!
1.2050 +//! @SYMTestType CIT
1.2051 +
1.2052 +START_TESTCASE SEC-UPS-E035
1.2053 +
1.2054 +// Delete Existing Database
1.2055 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2056 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2057 +
1.2058 +// Case 1:
1.2059 +
1.2060 +// Client call to UPS invoking the defualt policy evaluator and selecting 'ALWAYS' from the dialog
1.2061 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Always
1.2062 +
1.2063 +// Initial check to ensure that DB contains an ALWAYS decision for the client with a NULL fingerprint
1.2064 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Alaways_initalCheck
1.2065 +
1.2066 +// Database Management Checking to ensure that each value in the decision is what is expected
1.2067 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Alaways_dbManagementCheck
1.2068 +
1.2069 +
1.2070 +// Case 2:
1.2071 +
1.2072 +// Client call to UPS invoking the defualt policy evaluator and selecting 'NEVER' from the dialog
1.2073 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Never
1.2074 +
1.2075 +// Initial check to ensure that DB contains an additional NEVER decision for the client with a NULL fingerprint
1.2076 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Never_initalCheck
1.2077 +
1.2078 +// Database Management Checking to ensure that each value in the decision is what is expected
1.2079 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Never_dbManagementCheck
1.2080 +
1.2081 +
1.2082 +// Database Import/Export Checking:
1.2083 +
1.2084 +// Shutdown UPS Server
1.2085 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2086 +
1.2087 +// Dump contents of the database
1.2088 +RUN_PROGRAM dumpupsdb.exe -e -db \private\10283558\database\ups.db -f c:\exportdb.db -s
1.2089 +
1.2090 +// Delete Existing UPS Database
1.2091 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2092 +
1.2093 +// Reimport Database Contents
1.2094 +RUN_PROGRAM dumpupsdb.exe -i -db \private\10283558\database\ups.db -f c:\exportdb.db -s
1.2095 +
1.2096 +// Delete Temporary Export File
1.2097 +RUN_UTILS DeleteFile c:\exportdb.db
1.2098 +
1.2099 +// Re Check the NULL fingerprint Decisions Imported into the Database
1.2100 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Alaways_initalCheck
1.2101 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Never_initalCheck
1.2102 +
1.2103 +// Final Datbase Management Check to ensure that the values of the Decision are still as expected
1.2104 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini invoke_default_policy_evaluator_Never_dbManagementCheck
1.2105 +
1.2106 +END_TESTCASE SEC-UPS-E035
1.2107 +
1.2108 +//! @SYMTestCaseID SEC-INTEG-UPS-E036
1.2109 +//! @SYMTestCaseDesc System Server Security
1.2110 +//! (System_Server_Security)
1.2111 +//!
1.2112 +//! @SYMPREQ PREQ1262
1.2113 +//! @SYMREQ REQ7408
1.2114 +//! @SYMTestPriority Critical
1.2115 +//! @SYMTestStatus Implemented
1.2116 +//! @SYMTestActions
1.2117 +//! Preconditions:
1.2118 +//! • There is an appropriate policy file in the phone that uses SystemServerSecurity
1.2119 +//! property set with different values for individual policies including
1.2120 +//! ESystemServerSecurityPassedOrFailed, ESystemServerSecurityFailed and
1.2121 +//! ESystemServerSecurityPassed.
1.2122 +//! Test Actions:
1.2123 +//! • Case 1: Request set services to a test system server to ensure that an individual
1.2124 +//! policy set with ESystemServerSecurityPassedOrFailed is invoked, use different
1.2125 +//! values for platSecPass parameter in authorize request.
1.2126 +//! • Case 2: : Request set services to a test system server to ensure that an
1.2127 +//! individual policy set with ESystemServerSecurityFailed is invoked, use values
1.2128 +//! for platSecPass parameter as EFalse in authorize request.
1.2129 +//! • Case 3: : Request set services to a test system server to ensure that an
1.2130 +//! individual policy set with ESystemServerSecurityPassed is invoked, use values for
1.2131 +//! platSecPass parameter as ETrue in authorize request.
1.2132 +//!
1.2133 +//! @SYMTestExpectedResults
1.2134 +//! • On each case the appropriate individual policy is invoked.
1.2135 +//!
1.2136 +//! @SYMTestType CIT
1.2137 +
1.2138 +START_TESTCASE SEC-INTEG-UPS-E036
1.2139 +
1.2140 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2141 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2142 +
1.2143 +// case 1
1.2144 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini ESystemServerSecurityPassedOrFailed
1.2145 +// case 2
1.2146 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini ESystemServerSecurityFailed
1.2147 +// case 3
1.2148 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini ESystemServerSecurityPassed
1.2149 +
1.2150 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini count_8
1.2151 +
1.2152 +END_TESTCASE SEC-INTEG-UPS-E036
1.2153 +
1.2154 +
1.2155 +
1.2156 +//********************** SEC-UPS-G : NEGATIVE TEST CASES **********************
1.2157 +
1.2158 +//! @SYMTestCaseID SEC-UPS-INTEG-G004
1.2159 +//! @SYMTestCaseDesc Non ProtServ capability system server
1.2160 +//! (no_protser_cap)
1.2161 +//!
1.2162 +//! @SYMPREQ PREQ1262
1.2163 +//! @SYMREQ REQ7427
1.2164 +//!
1.2165 +//! @SYMTestPriority Critical
1.2166 +//! @SYMTestStatus Implemented
1.2167 +//! @SYMTestActions Preconditions:
1.2168 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.2169 +//! service offered by the “system server”.
1.2170 +//! • The system server request prompt to UPS does NOT have ProtServ capability.
1.2171 +//!
1.2172 +//! Test Actions:
1.2173 +//! • Launch “test client” which tries to connect to a system server and use service.
1.2174 +//! • System server asks for a user prompt to the UPS (Authorise method).
1.2175 +//! • UPS should deny the request from system server.
1.2176 +//!
1.2177 +//! @SYMTestExpectedResults • System server receives a KErrPermissionDenied from Ups.
1.2178 +//!
1.2179 +//! @SYMTestType CIT
1.2180 +
1.2181 +START_TESTCASE SEC-UPS-INTEG-G004
1.2182 +RUN_TEST_STEP 100 TUPSInteg_1 NonProtServAuthorisation z:\tups\integ\scripts\tups_integ.ini no_protser_cap
1.2183 +// test variation: server has no capabilities but plat sec test passed
1.2184 +// Note: nop decision is stored or dialog prompted.
1.2185 +RUN_TEST_STEP 100 TUPSInteg_1 NonProtServAuthorisation z:\tups\integ\scripts\tups_integ.ini no_protser_cap_b
1.2186 +END_TESTCASE SEC-UPS-INTEG-G004
1.2187 +
1.2188 +
1.2189 +//! @SYMTestCaseID SEC-UPS-G007
1.2190 +//! @SYMTestCaseDesc Protected deletion and update of decisions.
1.2191 +//! (remove_update_capabilityChecking)
1.2192 +//!
1.2193 +//! @SYMPREQ PREQ1262
1.2194 +//! @SYMREQ REQ7381
1.2195 +//!
1.2196 +//! @SYMTestPriority Critical
1.2197 +//! @SYMTestStatus Implemented
1.2198 +//! @SYMTestActions Preconditions:
1.2199 +//! • Existence of test application 1 without AllFiles capabilities.
1.2200 +//! • Existence of test application 2 without WriteDeviceData capabilities.
1.2201 +//!
1.2202 +//! Test Actions:
1.2203 +//! • Instruct test application 1 to attempt a record update in decision database using UpsManagement.
1.2204 +//! • Instruct test application 2 to attempt a record delete in decision database using UpsManagement.
1.2205 +//!
1.2206 +//! @SYMTestExpectedResults • Test application1 should not be able to update record.
1.2207 +//! • Test application2 should not be able to delete record.
1.2208 +//!
1.2209 +//! @SYMTestType CIT
1.2210 +
1.2211 +
1.2212 +START_TESTCASE SEC-UPS-G007
1.2213 +
1.2214 +// Delete Existing Database
1.2215 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2216 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2217 +
1.2218 +// populate decision database with sample inital values.
1.2219 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.2220 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.2221 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.2222 +
1.2223 +// Perform initial checking on sample decisions
1.2224 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.2225 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.2226 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.2227 +
1.2228 +// * STAGE 1 - UPDATE RECORD CAPABILITY TEST (AllFiles Required)
1.2229 +
1.2230 +// Perform attempt to update a decision "WITHOUT" the appropriate capabilities
1.2231 +RUN_TEST_STEP !Result=-46 100 TUPSInteg_writedevice UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_Update
1.2232 +
1.2233 +// Run Database Management Checking for Unauthorised Update
1.2234 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_unauthorisedUpdate_DBCheck
1.2235 +
1.2236 +// Perform attempt to update a decision "WITH" the appropriate capabilities
1.2237 +RUN_TEST_STEP 100 TUPSInteg_allfiles_readdevice UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_Update
1.2238 +
1.2239 +// Run Database Management Checking for authorised Update
1.2240 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_authorisedUpdate_DBCheck
1.2241 +
1.2242 +
1.2243 +// * STAGE 2 - REMOVE RECORD CAPABILITY TEST (WriteDeviceData Required)
1.2244 +
1.2245 +// Perform attempt to remove a decision "WITHOUT" the appropriate capabilities
1.2246 +RUN_TEST_STEP !Result=-46 100 TUPSInteg_allfiles_readdevice UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_Remove
1.2247 +
1.2248 +// Run Database Management Checking for Unauthorised Remove
1.2249 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_unauthorisedRemove_DBCheck
1.2250 +
1.2251 +// Perform attempt to remove a decision "WITH" the appropriate capabilities
1.2252 +RUN_TEST_STEP 100 TUPSInteg_writedevice UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_Remove
1.2253 +
1.2254 +// Run Database Management Checking for authorised Remove
1.2255 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini remove_update_capabilityChecking_authorisedRemove_DBCheck
1.2256 +
1.2257 +END_TESTCASE SEC-UPS-G007
1.2258 +
1.2259 +
1.2260 +//! @SYMTestCaseID SEC-UPS-INTEG-G008
1.2261 +//! @SYMTestCaseDesc Policy Evaluator Leaving
1.2262 +//! (policy_evaluator_leave)
1.2263 +//!
1.2264 +//! @SYMPREQ PREQ1262
1.2265 +//! @SYMREQ REQ7427
1.2266 +//! @SYMTestPriority Critical
1.2267 +//! @SYMTestStatus Implemented
1.2268 +//! @SYMTestActions Preconditions:
1.2269 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.2270 +//! service offered by the “system server”.
1.2271 +//! • Test Client doesn’t have any decision stored in DB related to service about to be used by test
1.2272 +//! client.
1.2273 +//!
1.2274 +//! Test Actions:
1.2275 +//! • Launch “test clients” which tries to use of system servers. System server should request UPS for
1.2276 +//! user security dialog.
1.2277 +//! • When UPS invokes policy evaluator, induce a “leave” in policy evaluator.
1.2278 +//! • UPS should process this leave from policy evaluator and reply with a silent denial to system
1.2279 +//! server.
1.2280 +//!
1.2281 +//! @SYMTestExpectedResults • System server receives a silent denial from UPS.
1.2282 +//!
1.2283 +//! @SYMTestType CIT
1.2284 +
1.2285 +//Delete Current Database
1.2286 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2287 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2288 +
1.2289 +START_TESTCASE SEC-UPS-INTEG-G008
1.2290 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_leave_session
1.2291 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_leave_always
1.2292 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_leave_never
1.2293 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_leave_yes
1.2294 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_leave_no
1.2295 +
1.2296 +CONCURRENT
1.2297 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_leaving_concurrent
1.2298 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_always_concurrent
1.2299 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini policyevaluator_never_concurrent
1.2300 +CONSECUTIVE
1.2301 +
1.2302 +END_TESTCASE SEC-UPS-INTEG-G008
1.2303 +
1.2304 +
1.2305 +//! @SYMTestCaseID SEC-UPS-INTEG-G009
1.2306 +//! @SYMTestCaseDesc Dialog Creator Leaving
1.2307 +//! (dialog_creator_leave)
1.2308 +//!
1.2309 +//! @SYMPREQ PREQ1262
1.2310 +//! @SYMREQ REQ7427
1.2311 +//!
1.2312 +//! @SYMTestPriority Critical
1.2313 +//! @SYMTestStatus Implemented
1.2314 +//! @SYMTestActions Preconditions:
1.2315 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.2316 +//! service offered by the “system server”.
1.2317 +//! • Test Client doesn’t have any decision stored in DB related to service about to be used by test
1.2318 +//! client.
1.2319 +//!
1.2320 +//! Test Actions:
1.2321 +//! • Launch “test clients” which tries to use of system servers. System server should request UPS for
1.2322 +//! user security dialog.
1.2323 +//! • When UPS invokes dialog, induce a “leave” in dialog creator.
1.2324 +//! • UPS should process this leave from policy evaluator and reply with a silent denial to system
1.2325 +//! server.
1.2326 +//!
1.2327 +//! @SYMTestExpectedResults • System server receives a silent denial from UPS.
1.2328 +//!
1.2329 +//! @SYMTestType CIT
1.2330 +
1.2331 +START_TESTCASE SEC-UPS-INTEG-G009
1.2332 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_leave_session
1.2333 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_leave_always
1.2334 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_leave_never
1.2335 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_leave_yes
1.2336 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_leave_no
1.2337 +
1.2338 +CONCURRENT
1.2339 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_leaving_concurrent
1.2340 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_always_concurrent
1.2341 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini dialogcreator_never_concurrent
1.2342 +CONSECUTIVE
1.2343 +
1.2344 +END_TESTCASE SEC-UPS-INTEG-G009
1.2345 +
1.2346 +
1.2347 +//! @SYMTestCaseID SEC-UPS-G010
1.2348 +//! @SYMTestCaseDesc Protected reading of decisions
1.2349 +//! (readDecision_capabilityChecking)
1.2350 +//!
1.2351 +//! @SYMPREQ PREQ1262
1.2352 +//! @SYMREQ REQ7492
1.2353 +//!
1.2354 +//! @SYMTestPriority Critical
1.2355 +//! @SYMTestStatus Implemented
1.2356 +//! @SYMTestActions Preconditions:
1.2357 +//! • There are some previous decisions stored in decision data base.
1.2358 +//! • Test application does not have ReadDeviceData but it has WriteDeviceData capabilities.
1.2359 +//!
1.2360 +//! Test Actions:
1.2361 +//! • Try to use test application with not ReadDeviceData capabilities to read existing entry from decision DB.
1.2362 +//!
1.2363 +//! @SYMTestExpectedResults • Reading of entry fails, test application is returned error.
1.2364 +//!
1.2365 +//! @SYMTestType CIT
1.2366 +
1.2367 +
1.2368 +START_TESTCASE SEC-UPS-G010
1.2369 +
1.2370 +// Delete Existing Database
1.2371 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2372 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2373 +
1.2374 +// populate decision database with sample inital values.
1.2375 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.2376 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.2377 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini populate_sample2
1.2378 +
1.2379 +// Perform initial checking on sample decisions
1.2380 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.2381 +RUN_TEST_STEP 100 TUPSInteg_2 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.2382 +RUN_TEST_STEP 100 TUPSInteg_3 UPSClientStep z:\tups\integ\scripts\tups_integ.ini check_sample2
1.2383 +
1.2384 +// Perform attempt to read a decision "WITHOUT" the appropriate capabilities
1.2385 +RUN_TEST_STEP !Result=-46 100 TUPSInteg_writedevice UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini readDecision_capabilityChecking_dbRead
1.2386 +
1.2387 +// Perform attempt to update a decision "WITH" the appropriate capabilities
1.2388 +RUN_TEST_STEP 100 TUPSInteg_readdevice UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini readDecision_capabilityChecking_dbRead
1.2389 +
1.2390 +END_TESTCASE SEC-UPS-G010
1.2391 +
1.2392 +
1.2393 +
1.2394 +//********************** SEC-UPS-H : MISCELLANEOUS **********************
1.2395 +
1.2396 +//! @SYMTestCaseID SEC-UPS-INTEG-H010
1.2397 +//! @SYMTestCaseDesc Simple request cancelation
1.2398 +//! (simple_cancel)
1.2399 +//!
1.2400 +//! @SYMPREQ PREQ1262
1.2401 +//! @SYMREQ REQ7427
1.2402 +//!
1.2403 +//! @SYMTestPriority Critical
1.2404 +//! @SYMTestStatus Implemented
1.2405 +//! @SYMTestActions Preconditions:
1.2406 +//! • There is an appropriate policy, policy evaluator and dialog creator that matches the UID of the
1.2407 +//! service offered by the “system server”.
1.2408 +//! • Test Client doesn’t have any decision stored in DB related to service about to be used by test
1.2409 +//! client.
1.2410 +//!
1.2411 +//! Test Actions:
1.2412 +//! • Launch “test clients” which tries to use of system servers. System server should request UPS for
1.2413 +//! user security dialog.
1.2414 +//! • When server requests UPS authorisation, cancel the request using CancelPrompt method.
1.2415 +//!
1.2416 +//! @SYMTestExpectedResults • System server receives a KErrCancel from Ups.
1.2417 +//!
1.2418 +//! @SYMTestType CIT
1.2419 +
1.2420 +START_TESTCASE SEC-UPS-INTEG-H010
1.2421 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini simple_cancel
1.2422 +END_TESTCASE SEC-UPS-INTEG-H010
1.2423 +
1.2424 +
1.2425 +//! @SYMTestCaseID SEC-UPS-H011
1.2426 +//! @SYMTestCaseDesc Reversible decision DB export by dumpupsdb
1.2427 +//! (Export_Import_DBDumpTool)
1.2428 +//!
1.2429 +//! @SYMPREQ PREQ1262
1.2430 +//! @SYMREQ REQ7443 REQ7442
1.2431 +//!
1.2432 +//! @SYMTestPriority Critical
1.2433 +//! @SYMTestStatus Implemented
1.2434 +//! @SYMTestActions Test Actions:
1.2435 +//! • Populate decision database with a reasonable number of decisions.
1.2436 +//! • Check correct behaviour of UPS with this decision DB.
1.2437 +//! • Stop UPS server running and use “dumpupsdb.exe” to export database to temporary file.
1.2438 +//! • Using dumpupsdb.exe” re-import this temporary file into the decision DB (ups.db).
1.2439 +//! • Check that re-imported decision database contains the same records that the original and UPS
1.2440 +//! behaves normally when using it.
1.2441 +//!
1.2442 +//! @SYMTestExpectedResults • There is no functional difference between the original decision database and the
1.2443 +//! re-imported one.
1.2444 +//!
1.2445 +//! @SYMTestType CIT
1.2446 +
1.2447 +START_TESTCASE SEC-UPS-H011
1.2448 +
1.2449 +// Delete Existing Database
1.2450 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2451 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2452 +
1.2453 +// Run the initial data entry step to populate the database with entries
1.2454 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Export_Import_DBDumpTool_Setup
1.2455 +
1.2456 +// Check the newly created Decisions within the UPS Database
1.2457 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Export_Import_DBDumpTool_Verify
1.2458 +
1.2459 +// Shutdown UPS Server
1.2460 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2461 +
1.2462 +// Dump contents of the database
1.2463 +RUN_PROGRAM dumpupsdb.exe -e -db \private\10283558\database\ups.db -f c:\exportdb.db -s
1.2464 +RUN_PROGRAM dumpupsdb.exe -e -db \private\10283558\database\ups.db -f c:\exportdba.txt -s
1.2465 +
1.2466 +// Delete Existing UPS Database
1.2467 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2468 +
1.2469 +// Reimport Database Contents
1.2470 +RUN_PROGRAM dumpupsdb.exe -i -db \private\10283558\database\ups.db -f c:\exportdb.db -s
1.2471 +RUN_PROGRAM dumpupsdb.exe -e -db \private\10283558\database\ups.db -f c:\exportdbb.txt -s
1.2472 +
1.2473 +// Delete Temporary Export File
1.2474 +RUN_UTILS DeleteFile c:\exportdb.db
1.2475 +
1.2476 +// Rerun service requests using Reimported Database
1.2477 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Export_Import_DBDumpTool_Verify
1.2478 +
1.2479 +/////////// repeats same test sequence with (-b) flag in dumpupsdb.exe
1.2480 +
1.2481 +// Delete Existing Database
1.2482 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2483 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2484 +
1.2485 +// Run the initial data entry step to populate the database with entries
1.2486 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Export_Import_DBDumpTool_Setup
1.2487 +
1.2488 +// Check the newly created Decisions within the UPS Database
1.2489 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Export_Import_DBDumpTool_Verify
1.2490 +
1.2491 +// Shutdown UPS Server
1.2492 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2493 +
1.2494 +// Dump contents of the database
1.2495 +RUN_PROGRAM dumpupsdb.exe -e -db \private\10283558\database\ups.db -f c:\exportdb.db -s -b
1.2496 +
1.2497 +// Delete Existing UPS Database
1.2498 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2499 +
1.2500 +// Reimport Database Contents
1.2501 +RUN_PROGRAM dumpupsdb.exe -i -db \private\10283558\database\ups.db -f c:\exportdb.db -s -b
1.2502 +
1.2503 +// Delete Temporary Export File
1.2504 +RUN_UTILS DeleteFile c:\exportdb.db
1.2505 +
1.2506 +// Rerun service requests using Reimported Database
1.2507 +RUN_TEST_STEP 100 TUPSInteg_1 UPSClientStep z:\tups\integ\scripts\tups_integ.ini Export_Import_DBDumpTool_Verify
1.2508 +
1.2509 +END_TESTCASE SEC-UPS-H011
1.2510 +
1.2511 +
1.2512 +//! @SYMTestCaseID SEC-UPS-INTEG-H012
1.2513 +//! @SYMTestCaseDesc UPS sub-session in different thread
1.2514 +//! (ups_session_shared)
1.2515 +//!
1.2516 +//! @SYMPREQ PREQ1262
1.2517 +//! @SYMREQ REQ7446
1.2518 +//! @SYMTestPriority Critical
1.2519 +//! @SYMTestStatus Implemented
1.2520 +//! @SYMTestActions Test Actions:
1.2521 +//! • Open an UPS session from a test server.
1.2522 +//! • Create a new thread and share UPS session with this new thread.
1.2523 +//! • From this new thread create a sub-session to ups, request authorisation to UPS
1.2524 +//! using this sub-session.
1.2525 +//! • Check that UPS behaves like normal and the appropriate decision is stored in DB.
1.2526 +//!
1.2527 +//! @SYMTestExpectedResults • Authorize method for UPS can be used successfully for thread different that
1.2528 +//! the one owning the UPS session.
1.2529 +//!
1.2530 +//! @SYMTestType CIT
1.2531 +
1.2532 +START_TESTCASE SEC-UPS-INTEG-H012
1.2533 +// Shutdown UPS Server
1.2534 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2535 +
1.2536 +// Delete Existing UPS Database
1.2537 +RUN_UTILS DeleteFile c:\private\10283558\database\ups.db
1.2538 +
1.2539 +RUN_TEST_STEP 100 TUPSInteg_minor Multithread z:\tups\integ\scripts\tups_integ.ini ups_session_shared
1.2540 +RUN_TEST_STEP 100 TUPSInteg_1 UPSDbManagementStep z:\tups\integ\scripts\tups_integ.ini count_2
1.2541 +
1.2542 +// Shutdown UPS Server
1.2543 +RUN_TEST_STEP 100 TUPSInteg_1 UtilsCloseUps
1.2544 +
1.2545 +// Dump contents of the database
1.2546 +RUN_PROGRAM dumpupsdb.exe -e -db \private\10283558\database\ups.db -f c:\multithread.db -s -b
1.2547 +END_TESTCASE SEC-UPS-INTEG-H012
1.2548 +
1.2549 +
1.2550 +//! @SYMTestCaseID SEC-UPS-MISC-0002
1.2551 +//! @SYMTestCaseDesc Clears off properties previously set for policy evaluators and dialog creators.
1.2552 +
1.2553 +START_TESTCASE SEC-UPS-MISC-0002
1.2554 +RUN_TEST_STEP 100 TUPSInteg_1 PropertyStep z:\tups\integ\scripts\tups_properties.ini PropertiesToDestroy
1.2555 +END_TESTCASE SEC-UPS-MISC-0002
1.2556 +
1.2557 +
1.2558 +PRINT Complete_TUPS_Tests