Note that there are some explanatory texts on larger screens.

plurals
  1. POStarting processes with different unlocked keychains on MacOS
    primarykey
    data
    text
    <p>As described in question <a href="https://stackoverflow.com/questions/8535832">CLI: Switch keychains in order to sign an xcodebuild</a> I have the problem of having to use two keychains for running <code>xcodebuild</code>. I need this because our enterprise &amp; appstore identities are called the same.</p> <p>When I try the proposed solution it works fine, if I'm running only one <code>xcodebuild</code>at a time. But I'm using a buildserver (hudson or jenkins) running multiple builds in parallel. Each build job should build the enterprise and the appstore version of an app, therefore it has to use different keychains. When changing the keychain list as proposed, this always affects all running processes of the current user. Therefore parallel builds of different projects would be affected and basically fail or use the wrong keychain.</p> <p>I've tried several workarounds to open a new security context, which seems to host the keychain information:</p> <ul> <li>I used <code>login -f ...</code> to start a new login session, hoping it will use an independent security context. But when I change the keychain settings in the session it also affects the other login session.</li> <li>I used <code>ssh localhost ...</code> to start a new login session, but unfortunately with the same result.</li> </ul> <p>It seems, that the security context is bound to the user and not to a dedicated session. Unfortunately I cannot find any information about those security contexts using Google.</p> <p>Is there any way to run several processes for a dedicated user having different keychains active and unlocked?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload