OSX custom authorization plugin breaks with upgrade to Mojave
We have a custom authorization plugin for OSX, written using this as our base:
https://github.com/skycocker/NameAndPassword
and referencing the official documentation where needed:
https://developer.apple.com/documentation/security/authorization_plug-ins/using_authorization_plug-ins
The plugin was working perfectly, until the Mojave release. With Mojave, our auth plugin UI does not draw and we only see the circular login arrow button. The only way to login is to ssh into the machine, uninstall our auth plugin and re-enable to default OSX login mechanism.
We added additional logging and found that the plugin is indeed being loaded and runs normally. It's just the UI that is not displaying anymore. My guess is that they have changed some requirements for custom auth plugins but have not updated the documentation.
Does anyone have any ideas as to why the UI might not be displaying in Mojave?
EDIT:
Some more information. We have found that we are able to tab through the controls that are part of our plugin. This implies that the controls are actually there, but are either off screen or maybe just not being drawn? Very strange indeed...
EDIT 2:
I tried building the NameAndPassword sample, and it displays fine in Mojave. This sample used a .nib for the interface, which I cannot edit in the recent version of xcode. So, I tried recreating the interface as a .xib and surprisingly, the UI for NameAndPassword is now gone as well!
So, there is perhaps something happening behind the scenes when the .xib file is compiled which is causing the UI to not be drawn, which is NOT happening with a .nib based interface.
objective-c macos plugins authorization macos-mojave
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
add a comment |
We have a custom authorization plugin for OSX, written using this as our base:
https://github.com/skycocker/NameAndPassword
and referencing the official documentation where needed:
https://developer.apple.com/documentation/security/authorization_plug-ins/using_authorization_plug-ins
The plugin was working perfectly, until the Mojave release. With Mojave, our auth plugin UI does not draw and we only see the circular login arrow button. The only way to login is to ssh into the machine, uninstall our auth plugin and re-enable to default OSX login mechanism.
We added additional logging and found that the plugin is indeed being loaded and runs normally. It's just the UI that is not displaying anymore. My guess is that they have changed some requirements for custom auth plugins but have not updated the documentation.
Does anyone have any ideas as to why the UI might not be displaying in Mojave?
EDIT:
Some more information. We have found that we are able to tab through the controls that are part of our plugin. This implies that the controls are actually there, but are either off screen or maybe just not being drawn? Very strange indeed...
EDIT 2:
I tried building the NameAndPassword sample, and it displays fine in Mojave. This sample used a .nib for the interface, which I cannot edit in the recent version of xcode. So, I tried recreating the interface as a .xib and surprisingly, the UI for NameAndPassword is now gone as well!
So, there is perhaps something happening behind the scenes when the .xib file is compiled which is causing the UI to not be drawn, which is NOT happening with a .nib based interface.
objective-c macos plugins authorization macos-mojave
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
Works fine for me on Mojave. I have a custom button in the login view and it displays and catches on click event fine. I have tried it on a VM but wouldn't think there would be a difference in behavior on a real hardware.
– Mahesh
Dec 19 '18 at 13:08
BTW, I tested on a clean installation of Mojave and not an upgrade from an earlier version of macOS.
– Mahesh
Dec 19 '18 at 13:15
Were you ever able to find a solution? I am experiencing the exact same problem, observing the same things you mention in EDIT and EDIT2.
– eckenrod
Jan 18 at 15:38
We did find a solution, though not an explanation. All I did was resize the window so that it was smaller, and suddenly everything showed up. I have not figured out or read about any size restrictions, but in any case, that's what made it work for us.
– Chris Giles
Jan 20 at 18:32
add a comment |
We have a custom authorization plugin for OSX, written using this as our base:
https://github.com/skycocker/NameAndPassword
and referencing the official documentation where needed:
https://developer.apple.com/documentation/security/authorization_plug-ins/using_authorization_plug-ins
The plugin was working perfectly, until the Mojave release. With Mojave, our auth plugin UI does not draw and we only see the circular login arrow button. The only way to login is to ssh into the machine, uninstall our auth plugin and re-enable to default OSX login mechanism.
We added additional logging and found that the plugin is indeed being loaded and runs normally. It's just the UI that is not displaying anymore. My guess is that they have changed some requirements for custom auth plugins but have not updated the documentation.
Does anyone have any ideas as to why the UI might not be displaying in Mojave?
EDIT:
Some more information. We have found that we are able to tab through the controls that are part of our plugin. This implies that the controls are actually there, but are either off screen or maybe just not being drawn? Very strange indeed...
EDIT 2:
I tried building the NameAndPassword sample, and it displays fine in Mojave. This sample used a .nib for the interface, which I cannot edit in the recent version of xcode. So, I tried recreating the interface as a .xib and surprisingly, the UI for NameAndPassword is now gone as well!
So, there is perhaps something happening behind the scenes when the .xib file is compiled which is causing the UI to not be drawn, which is NOT happening with a .nib based interface.
objective-c macos plugins authorization macos-mojave
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
We have a custom authorization plugin for OSX, written using this as our base:
https://github.com/skycocker/NameAndPassword
and referencing the official documentation where needed:
https://developer.apple.com/documentation/security/authorization_plug-ins/using_authorization_plug-ins
The plugin was working perfectly, until the Mojave release. With Mojave, our auth plugin UI does not draw and we only see the circular login arrow button. The only way to login is to ssh into the machine, uninstall our auth plugin and re-enable to default OSX login mechanism.
We added additional logging and found that the plugin is indeed being loaded and runs normally. It's just the UI that is not displaying anymore. My guess is that they have changed some requirements for custom auth plugins but have not updated the documentation.
Does anyone have any ideas as to why the UI might not be displaying in Mojave?
EDIT:
Some more information. We have found that we are able to tab through the controls that are part of our plugin. This implies that the controls are actually there, but are either off screen or maybe just not being drawn? Very strange indeed...
EDIT 2:
I tried building the NameAndPassword sample, and it displays fine in Mojave. This sample used a .nib for the interface, which I cannot edit in the recent version of xcode. So, I tried recreating the interface as a .xib and surprisingly, the UI for NameAndPassword is now gone as well!
So, there is perhaps something happening behind the scenes when the .xib file is compiled which is causing the UI to not be drawn, which is NOT happening with a .nib based interface.
objective-c macos plugins authorization macos-mojave
objective-c macos plugins authorization macos-mojave
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
edited Nov 13 '18 at 23:14
Chris Giles
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
asked Nov 12 '18 at 22:57
Chris GilesChris Giles
112
112
Works fine for me on Mojave. I have a custom button in the login view and it displays and catches on click event fine. I have tried it on a VM but wouldn't think there would be a difference in behavior on a real hardware.
– Mahesh
Dec 19 '18 at 13:08
BTW, I tested on a clean installation of Mojave and not an upgrade from an earlier version of macOS.
– Mahesh
Dec 19 '18 at 13:15
Were you ever able to find a solution? I am experiencing the exact same problem, observing the same things you mention in EDIT and EDIT2.
– eckenrod
Jan 18 at 15:38
We did find a solution, though not an explanation. All I did was resize the window so that it was smaller, and suddenly everything showed up. I have not figured out or read about any size restrictions, but in any case, that's what made it work for us.
– Chris Giles
Jan 20 at 18:32
add a comment |
Works fine for me on Mojave. I have a custom button in the login view and it displays and catches on click event fine. I have tried it on a VM but wouldn't think there would be a difference in behavior on a real hardware.
– Mahesh
Dec 19 '18 at 13:08
BTW, I tested on a clean installation of Mojave and not an upgrade from an earlier version of macOS.
– Mahesh
Dec 19 '18 at 13:15
Were you ever able to find a solution? I am experiencing the exact same problem, observing the same things you mention in EDIT and EDIT2.
– eckenrod
Jan 18 at 15:38
We did find a solution, though not an explanation. All I did was resize the window so that it was smaller, and suddenly everything showed up. I have not figured out or read about any size restrictions, but in any case, that's what made it work for us.
– Chris Giles
Jan 20 at 18:32
Works fine for me on Mojave. I have a custom button in the login view and it displays and catches on click event fine. I have tried it on a VM but wouldn't think there would be a difference in behavior on a real hardware.
– Mahesh
Dec 19 '18 at 13:08
Works fine for me on Mojave. I have a custom button in the login view and it displays and catches on click event fine. I have tried it on a VM but wouldn't think there would be a difference in behavior on a real hardware.
– Mahesh
Dec 19 '18 at 13:08
BTW, I tested on a clean installation of Mojave and not an upgrade from an earlier version of macOS.
– Mahesh
Dec 19 '18 at 13:15
BTW, I tested on a clean installation of Mojave and not an upgrade from an earlier version of macOS.
– Mahesh
Dec 19 '18 at 13:15
Were you ever able to find a solution? I am experiencing the exact same problem, observing the same things you mention in EDIT and EDIT2.
– eckenrod
Jan 18 at 15:38
Were you ever able to find a solution? I am experiencing the exact same problem, observing the same things you mention in EDIT and EDIT2.
– eckenrod
Jan 18 at 15:38
We did find a solution, though not an explanation. All I did was resize the window so that it was smaller, and suddenly everything showed up. I have not figured out or read about any size restrictions, but in any case, that's what made it work for us.
– Chris Giles
Jan 20 at 18:32
We did find a solution, though not an explanation. All I did was resize the window so that it was smaller, and suddenly everything showed up. I have not figured out or read about any size restrictions, but in any case, that's what made it work for us.
– Chris Giles
Jan 20 at 18:32
add a comment |
1 Answer
1
active
oldest
votes
Do you have this flag enabled : self.window?.canBecomeVisibleWithoutLogin = true
answered Nov 14 '18 at 10:30
dhruvdhruv
174
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271308%2fosx-custom-authorization-plugin-breaks-with-upgrade-to-mojave%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Do you have this flag enabled : self.window?.canBecomeVisibleWithoutLogin = true
answered Nov 14 '18 at 10:30
dhruvdhruv
174
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
add a comment |
Do you have this flag enabled : self.window?.canBecomeVisibleWithoutLogin = true
answered Nov 14 '18 at 10:30
dhruvdhruv
174
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
add a comment |
Do you have this flag enabled : self.window?.canBecomeVisibleWithoutLogin = true
answered Nov 14 '18 at 10:30
dhruvdhruv
174
Do you have this flag enabled : self.window?.canBecomeVisibleWithoutLogin = true
answered Nov 14 '18 at 10:30
dhruvdhruv
174
answered Nov 14 '18 at 10:30
dhruvdhruv
174
answered Nov 14 '18 at 10:30
dhruvdhruv
174
answered Nov 14 '18 at 10:30
dhruvdhruv
174
174
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
add a comment |
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
Please do not post additional questions as an answer but rather as a comment.
– Les Nie
23 hours ago
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271308%2fosx-custom-authorization-plugin-breaks-with-upgrade-to-mojave%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Works fine for me on Mojave. I have a custom button in the login view and it displays and catches on click event fine. I have tried it on a VM but wouldn't think there would be a difference in behavior on a real hardware.
– Mahesh
Dec 19 '18 at 13:08
BTW, I tested on a clean installation of Mojave and not an upgrade from an earlier version of macOS.
– Mahesh
Dec 19 '18 at 13:15
Were you ever able to find a solution? I am experiencing the exact same problem, observing the same things you mention in EDIT and EDIT2.
– eckenrod
Jan 18 at 15:38
We did find a solution, though not an explanation. All I did was resize the window so that it was smaller, and suddenly everything showed up. I have not figured out or read about any size restrictions, but in any case, that's what made it work for us.
– Chris Giles
Jan 20 at 18:32