Plugin:org.tolven.api

From DOC

Jump to: navigation, search

Contents

Version 2.1 Notes

Version 2.1.9

  • Added dataextract to the manifest as a required plug-in.
  • Added referencedBy RS API.

Version 2.1.8

  • Added the following chain filters:
    • apientervf,org.tolven.api.security.EnterVestibuleFilter
    • apiexitvf,org.tolven.api.security.ExitVestibuleFilter
    • apiselectvf,org.tolven.api.security.SelectAccountVestibuleFilter
  • Added XAccountFactory and xAccountUsers.xsd which allow a list of accounts to be returned to RS clients as XML.
  • Moved all RS resource classes and resource writers from org.tolven.jaxrs to org.tolven.api>
  • Added RS calls for the following APIs:
    • /vestibule/accountList
    • /vestibule/createAccount
    • /vestibule/selectAccount

Version 2.1.7

  • Replaced the <listener>, <filter>, and <servlet> deployment descriptor tags in the web-fragment.xml and web.xml files with @WebListener, @WebFilter, and @WebServlet in cases where order is not important.
  • Removed the "classes" extension for contributing classes to a war file's WEB-INF/classes directory to instead use a WEB-INF-LIB extension to contribute a jar containing those classes to the WEB-INF/lib directory of the war file.
  • APIServletContextListener now registers the following Shiro filters: apiaf,org.tolven.api.security.AccountFilter.
  • Added to APIServletContextListener the shiroRealm: tolven,org.tolven.gatekeeper.client.realm.GatekeeperClientRealm.
  • Added to APIServletContextListener the shiroFilter: apiaf,org.tolven.api.security.AccountFilter.
  • Changed annotation @Produces(Mediatype.APPLICATION_FORM_URLENCODED) to simply @Produces, because in no case was a form returned.
  • Fixed the Select Account and Select Account User functions on the Tolven Vestibule page.
  • Fixed a known issue about the Show Account List.
  • Fixed a known issue about the Login/Logout.

Version 2.1.6

  • Removed the <servlet> and <servlet-mapping-contribution> extensions from the manifests, and instead we now supply the servlet information via a web-fragment.xml file.
  • Added a ServletContextListener which logs when the module is successfully deployed with the war file.

Version 2.1.5

  • Corrected package name typo: org.tolven.exception.
  • Changed exception name from Gatekeeper*Exception to Tolven*Exception.

Version 2.1.4

  • Removed @ManagedBean because the new version of Jersey causes issues with injection. This was seen originally in JBoss, and is now seen in Glassfish as well.
  • Removed openssoclientsdk.jar, which is not used in Shiro.

Version 2.1.2

  • Updated the war services section of the manifest.
  • Removed unused TransactionFilter class. Its functionality is now managed by TolvenShiroFilter.
  • Vestibule functionality has been moved from the vestibule classes (now unused and removed) to AccountFilter.
  • The tolvenAPI.war file is no longer included in the zip, because it is now assembled by the TPF.
  • Deleted XAccountUserFactory, XFacadeACcountUserFactory, XPropertiesFactory.

Version 2.1.1

  • Added TolvenRequest class to provide request scope access to tolvenNow, TolvenUser, AccountUser, timezone, and locale.

Version 2.1.0

  • Added warModule-declaration extension-point, which identifies this plug-in as one which supplies a warModule assembly function to ear files. In this case, the default is tolvenAPI.war supplied to tolven.ear.
  • Added a number of WAR services suffixed with the word "adaptor", which are much like the previous extension-points for contributing to a war file, except that these take a source plug-in ID, so that contributions can be made from a plug-in other than the one which contains the actual contributed files. For example:

<extension id="org.tolven.api-WEB-INF-LIB-adaptor" plugin-id="org.tolven.api" point-id="WEB-INF-LIB-adaptor"> <parameter id="source-plugin-id" value="org.tolven.shiroweb" /> <parameter id="extension-point" value="shiroWEB" /> </extension> </pre>


Even though another plug-in does not have any of its own files to contribute to org.tolven.api, it can have the above in its manifest. This means that the files found in the org.tolven.shiroweb plug-in at the extension-point called shiroWEB that points to the warModule plug-in org.tolven.api.

The manifest also defines the following extension, where the webContextId (tolvenapi) can be used to identify this particular war file functionality in the context of TolvenGateKeeper. 

<extension id="env-entry-webContextId" plugin-id="org.tolven.component.war" point-id="env-entry">
<parameter id="env-entry-name" value="webContextId" />
<parameter id="env-entry-type" value="java.lang.String" />
<parameter id="env-entry-value" value="tolvenapi" />
<parameter id="target-plugin-id" value="org.tolven.api" />
</extension>
  • The TransactionFilter entry has now been incorporated into either the TolvenShiroFilter or the OpenAMSessionWrapperFilter. Only the appropriate one now gets contributed for a given installation.
  • Swapped look-ups from using the following as a prefix: 
java:global/tolven/tolvenAPI

to instead use: 

java:app/tolvenAPI

This way, the name of the application ear file (in this case "tolven") is not locked into the code for look-up.

  • Obtaining session information is now no longer done by TolvenSSO.getInstance(), and has now been replaced by an interface: TolvenSessionWrapperFactory.getInstance(), which will work for both Shiro and OpenAM.

Version 2 Notes

Version 2.0.29

  1. In default Tolven, the keysOptional feature is set to false. This means that only a user with a serCertificate/userPKCS12 attribute in LDAP can create Accounts or be added to an Account in Tolven. If true, a user without a serCertificate/userPKCS12 attribute in LDAP cannot create Accounts or be added to an Account in Tolven.
  2. Allow a user to be re-invited to an Account if there is a need to change their user keys.
  3. When multiple messages are queued, they are all queued using one connection.
  4. Added EndpointPoolResizeCount=1 because the default of 8 causes the EndpointPoolMaxSize to be ineffective because Glassfish re-sizes past it.
  5. Removed tolven-create-ddl.sql and tolven-drop-ddl.sql from the eclipselink section of persistence.xml because it prevents tables from being created.
  6. Lobs now used for: AccountMenuStructure.menuEventHandlerData, MSColumn.fromDocument, TolvenReport.
  7. Fixed bug in embedded classes definitions in ORM.
  8. Ensured queries match JPQL (hibernate compensated previously).
  9. Now for compilation, refers to own copy of jaxb, which has been upgraded to 2.2.
  10. Build file no longer refers to the tolven project.
  11. Fixed bug in the order of <provider> and <jta-data-source> in persistence.xml when option is used.
  12. Changed the ejb-jar.xml stanza to refer to v3.1.
  13. LDAPBean is not currently used, so we commented the loading of its properties, which are not deployed.

Version 2.0.28

  1. JIRA-TOLVENCORE-12: on login, the user gets a page that says "exit.html This Page should not be visible"
  2. Occurs when user has previously opted for a default Account

Version 2.0.27

  1. Added a test method for API calls

Version 2.0.26

  1. Added debug statements
  2. Redirect requires a starting forward slash (according to Glassfish)

Version 2.0.25

  1. ExitVestibule no longer needed, now the exit is achieved at the selectAccount stage (with one less redirect required)

Version 2.0.24

  1. Placed XFacadeAccountUsers in HttpSession to improve performance
  2. Renamed VestibuleResource to VestibuleResources to maintain *Resources pattern

Version 2.0.23

  1. Fixed bug where account type was not displayed on selectAccount page

Version 2.0.22

  1. Removed class org.tolven.server.RESTfulClient. The Jersey client is now accessible directly from in the ServletContext

Version 2.0.20

  1. Removed unnecessary code

Version 2.0.18

  1. Fixed bug in setting default account
  2. Added userContext, vestibulePass to the response on entering Vestibule
  3. Added userContext to the response on exiting Vestibule
  4. On selectAccount in the API, user automatically exits Vestibule

Version 2.0.17

  1. XAccountUser is sent from tolvenAPI to tolvenWeb in the Jersey response as an XML as opposed to storing it in the SSO session. It is stored in the HttpSession in tolvenWeb
  2. System properties, account user properties, etc are sent from tolvenAPI to tolvenWeb in a Jersey response as an XML
  3. All properties in tolvenWeb are now part of TolvenResourceBundle which is stored in the HttpSession, and can be accessed via JSF or Java POJOs

Version 2.0.16

  1. Resolved all properties for AccountUser, which are now added to the properties list of XAccountUser

Version 2.0.15

  1. Removed @Singleton beans in favor or simple Java singleton classes, since no caching is taking place, which will reduce the resource overhead

Version 2.0.14

  1. Renamed APIGeneralSecurityFilter to GeneralSecurityFilter (api already in package name)
  2. Removed TolvenUserVestibule since functionality is now part of GeneralSecurityFilter
  3. Consolidated Vestibule by moving vestibule functionality from tolvenWeb to tolvenAPI

Version 2.0.13

  1. Added security constraint for vestibule in tolvenAPI

Version 2.0.12

  1. Adding code to propagate the swap from Entity Beans to XML objects in tolvenWeb.war

Version 2.0.11

XAccountUser and XFacadeAccountUser are now passed between tolvenAPI and tolvenWeb instead of AccountUser

Version 2.0.9

  1. Session is now invalidated via the SSO session as opposed to the HttpSession
  2. Vestibule processing code clarified

Version 2.0.8

  1. System.getProperty replaced with tolvenPropertiesBean.getProperty, which ensures properties are initialized

Version 2.0.7

  1. Vestibule classes are now @ManagedBean classes

Version 2.0.6

  1. Users are now activated (TovenUser created), when they first login into Tolven, as per version V0
Facts about Plugin:org.tolven.apiRDF feed
Retrieved from "http://wiki.tolven.org/doc/index.php/Plugin:org.tolven.api"
Personal tools