1) Si2 uses Auth0 for user authentication. Recently, Auth0 implemented necessary heightened security for 1) leaked passwords and 2) brute-force login attempts.
IF YOU GET AN ERROR ON LOGIN ( Note: AT TOP of Login Form ) ---- AND SEE one of these POSSIBLE error messages:
Possible Error Message: password-leak. This error indicates that a password, used by the same user-name or user email-address, was leaked from a different site. IF you get this error!! You must change your Si2 password.
Possible Error Message: too_many_attemps. TEN consecutive, unsuccessful, login attemps will cause a block on an account.
IF you get this error!! YOU MUST CONTACT Si2 to UNBLOCK your account at Auth0.
2) NEW SIGNED LICENSE Will Be NEEDED: Si2 OpenAccess Extension Downloads, like oaScript and oaxPop, currently require the signed OpenAccess ESG License v 2.0 January 31, 2013. This license is being replaced SOON by the
OpenAccess ESG License V2.0.1 (March 15, 2017).
Your company should download, sign, and submit OpenAccess ESG License V2.0.1 (March 15, 2017). See See License Information Here!
1.
What is OpenAccess?
OpenAccess is a community effort to provide true interoperability versus
data exchange among IC design tools through an open standard data access
interface (API) and Reference Implementation supporting that. Return to Questions
2.
What is being standardized?
The API and its data model represent the standard.
The Reference Implementation is provided as
a service to provide a production grade solution
"out-of-the-box" for those who wish to take advantage of it and
as the "golden" model of compliant behavior. Return to Questions
3.
Must I use the Reference Implementation to be compliant to the standard?
NO. The Reference Implementation is being provided as a service
that may be used for your solution but need not be. Only the API defines
the standard and only the API need be used to be compliant. However, if
cases arise where the API is found to be incomplete or ambiguous, the
Reference Implementation's will define the standard behavior. Return to Questions
4.
Can there be other OpenAccess API implementations?
YES. Anyone can implement a database and put the OpenAccess API on
it. Restrictions are specified in the OpenAccess licenses.
In particular, the Reference Implementation source code is
copyrighted property that may be used by the licensee -- however, this
does not give one rights to copy that code into another OA
implementation. Return to Questions
7.
What is the history of OpenAccess?
The OpenAccess coalition was formed in Q4 1999. The members issued a
request-for-technology for existing technology, looking for a solution
that was proven and would be commercially adopted, and that supported a
broad set of EDA tools. As a result, the Cadence Genesis database and API
was selected and now forms the technology base for OpenAccess. Return to Questions
