More details can be found here:
http://community.versionone.com/KnowledgeBase/FAQs/Q11439.aspx
Thanks,
KC
--
You received this message because you are subscribed to the Google Groups "VersionOne-users" group.
To post to this group, send email to versiono...@googlegroups.com.
To unsubscribe from this group, send email to versionone-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/versionone-users?hl=en.
We were having issues with SSO implementation recommended below after we
upgraded to the Winter 12 release.
As such we reverted to a custom forms authentication "wrapper" for SSO
and needed to hide the password fields from the user which is what I
suspect you are trying to do.
I would highly recommend, if at all possible, to use the recommended
approach.
Please note that the knowledge base article does not mention that forms
authentication must be enabled on the VersionOne application in the
Winter 12 release, whereas in previous versions it did not.
Having said that, removing the password fields is fairly simple:
1. Back up any and all files you touch.
2. Edit the Default.aspx file in the VersionOne directory. Between the
tags V1Controls and body add a script block:
<script type="text/javascript">
$(document).ready(function(){
$('[id*="PasswordMember"]').css('display','none');
});
</script>
3. In the MetaRender sub folder of the VersionOne directory edit the
_omni_box.spark file:
In the div marked with the class="member-menu" remove the anchor tag
for the password menu option.
Recycle your app pool(s) and restart the website, or do an IIS reset.
You should no longer see password fields anywhere in the application.
Good Luck!
Our support team is actively working with SAIC/Harry to resolve the SSO issues they're experiencing; I/they will send an update to this group once we get to the root cause. But in the meantime we do not recommend (and cannot support) modifying the web application configuration or any aspx/js/css/other files - those changes will not be preserved during an update/upgrade (but the user.config file will).
Regards,
Ian Culling