This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out.
Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved.
Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement.
Terms of Use |
Privacy Policy |
Trademarks |
Patents |
Contact Us
Actually, SPF-I-676 and SPF-I-932 is not about the same thing.
The HTTP Basic/HTML Form authentication method (also known as username and password authentication) is being used for both Spotfire database accounts and LDAP accounts. SPF-I-932 is about combining for example HTTP Basic/HTML Form authentication with Kerberos authentication.
We have added support for combining Spotfire database accounts with LDAP accounts to 7.11, so I suggest rephrasing this idea and "unmerging" the two ideas. This idea can then be "closed" (or whatever the appropriate action is).
And Christian is correct, the Sites feature can be used in current systems to fix the problem described in SPF-I-932, but it is not the real solution to the problem. That remains to be implemented.
Christian, I'm interested to know what you would like to have seen differently, or what you were hoping for. I sent you an email
I think this is implemented in 7.9 with the new Sites feature. Not exactly what we were hoping for but there it is anyway.
https://docs.tibco.com/pub/spotfire_server/7.9.0/doc/html/TIB_sfire_server_tsas_admin_help/GUID-EC9DEFE0-C31F-48DF-8E13-11D8E4856E2D.html
good catch. Merging.
Similar to SPF-I-932?