Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 427434 - Our nativ win exe must be signed to access windows store apps
Summary: Our nativ win exe must be signed to access windows store apps
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 425266
  Show dependency tree
 
Reported: 2014-02-05 02:39 EST by Marvin Mueller CLA
Modified: 2015-03-24 03:54 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marvin Mueller CLA 2014-02-05 02:39:57 EST
It is important that our nativ rc exe is signed.
This is due restrictions with accessing the windows store apps with the automation framework and to have our application in front of apps.

Wee need the exe signed because of the following reason:
- Access to the automation tree of windows store apps
- for Object mapping mode we need to have a window which is on top of the app (for the border we are using to show the user the component is mappable and to get the position of the mouse pointer at the moment of mapping)
Comment 1 Marvin Mueller CLA 2014-02-11 02:44:26 EST
For further information read the following page[1]. We have set the uiAcess flag  to true because we need it for a topmost window in our object mapping mode.

[1] http://msdn.microsoft.com/en-us/library/windows/desktop/ee671610%28v=vs.85%29.aspx#uiaccess_requirements_for_assistive_technology_applications_
Comment 2 Alexandra Schladebeck CLA 2014-02-11 11:17:00 EST
Marvin, if I'm right, this hasn't been done yet - is that correct?
Comment 3 Marvin Mueller CLA 2014-02-17 02:09:47 EST
This has been done with an own generated certificate, but we should use an official certificate for the signing process to have a more easy setup.
Comment 4 Markus Tiede CLA 2014-05-26 04:41:57 EDT
While testing JUB-435 I noticed that the certificate being used is still an internal one (expiring: Tue Sep 23 23:08:50 2014).
Comment 5 Markus Tiede CLA 2015-03-24 03:54:48 EDT
We're currently no longer planning / working on adding support for this.