Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug OS-Chrome
New issue 405544 by
jus...@clearlogin.com: SAML SSO Integration API not
reliable with Chrome OS
http://code.google.com/p/chromium/issues/detail?id=405544
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/36.0.1985.143 Safari/537.36
Platform: 5841.98.0 (Official Build) stable-channel daisy
Steps to reproduce the problem:
1. Enable sso for chrome devices
2. Log out of an account or reboot the device
3. Try to add an sso enabled account
What is the expected behavior?
The google.principal.initialize function should properly identify the
device as a chrome device
What went wrong?
The function either is unsuccessful or not called, or at least is not
calling its callback to properly identify the device as a chrome device.
If you cancel adding a user and go to add one again, it works.
Did this work before? No
Chrome version: 36.0.1985.143 Channel: stable
OS Version: 36.0.1985.143
Flash Version: 14.0.0.177-r1
This is the code I am using:
<script type="text/javascript"
src="
https://ssl.gstatic.com/accounts/chrome/users-1.0.js"></script>
<script type="text/javascript">
function debug_msg(msg){
$('#debug-window').append(msg);
}
$(document).ready(function(){
debug_msg('document ready. ');
google.principal.initialize(function(){
debug_msg('this is chrome os. ');
});
});
</script>
Is there a way to expose a javascript console during this process? Couldn't
figure that out hence the manual debug messages.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings