App Broker Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Summary This article provides a list mapping the external App Portal version names to the version numbers. Synopsis This article provides a list mapping the external App Portal version names to the version numbers Discussion Product Name Release Version Product Internal Version Release Date App Portal 2019 R1 14.0.xx Mar-2019   2018 R1 13.0.xx Oct-2018   2017 R2 12.5.xx Dec-2017   2017 R1 12.0.xx July-2017   2016 11.0.xx Aug-2016   2015 R2 10.0.xx Nov-2015   2015 9.5.xx Jan-2015   2014 9.0.xx Jun-2014   2013 R2 8.5.xx Dec-2013   2013 8.1.xx Jun-2013   7.5 7.5.xx Dec-2012   7.x 7.x May-2012 SCCM Expert 6.5 6.5 Mar-2012
View full article
Summary This article descibes additional changes that are required after a password change is done for the App Portal Service account. Synopsis This article describes additional changes that are required after a password change is done for the App Portal Service account. Discussion Some organizations have a security policy that require account passwords to be changed periodically. If the App Portal Service account's password is changed, the new password would need to specified in the following areas: 1) For the ESDService under the services view - Stop the service - on the "Log On" tab, re-enter the account info with the new password - Restart the service 2) In IIS manager, under application pools. select SelfService. - Click on Advanced settings - For the Identity field, click on the ellipsis and for the custom account, specify the account name with new password   3) If using the App Portal Service account for forests/domain in the Active Directory view of App Portal the password at that location needs to be changed - Click Admin -> Site Management -> Active Directory -> Integration - Check the configuration for each forest and domain to see if App Portal Service account is being used and change password as needed 4) Do an IISRESET from an admin command prompt window 5) Update the account running the following My Apps Scheduled tasks under the Task Scheduler | Task Scheduler Library App Portal - Process Computers for My Apps Alerts App Portal - Send out My Apps Email Notifications Additional Information To change the password for the App pools and sites please open IIS and perform the following: 1) Open IIS 2) Select Application Pools in the Connections tree 3) Select the Application Pool 4) Right Click and select Advance Settings. 5) Find Process Model / Identity. The default may read ApplicationPoolIdentity 6) Click to the value (e.g. ApplicationPoolIdentity) 7) Click the ellipsis that appears to the right 8) Select a built in account or click custom account 9) If Custom account was chosen, click Set and specify the Windows account and password 10) Click OK to close the Set Credentials dialog 11) Click OK to close the Application Pool Identity dialog 12) Click OK to close the Advanced Settings dialog. 13) Recycle the Application Pool. For sites please navigate to each site and change the authentication settings as appropriate.
View full article
Application Version General Availability End of Standard Lifecycle End of Limited Lifecycle Lifecycle as of Today App Portal 2019 R1 2019-03-26 2021-03-26 2020-03-26 Standard Life Cycle App Portal 2018 R1 2018-10-25 2021-10-25 2019-10-25 Standard Life Cycle App Portal 2017 R2 2017-12-26 2020-12-26 2018-12-26 Standard Life Cycle App Portal 2017 2017-07-18 2020-07-18 2021-07-18 Standard Life Cycle App Portal 2016 2016-08-09 2019-08-09 2020-08-09 Standard Life Cycle App Portal 2015 R2 2015-11-03 2018-11-30 2019-11-30 Limited Life Cycle App Portal 2015 2015-01-29 2018-01-31 2019-01-31 No Support App Portal 2014 2014-06-05 2017-06-30 2018-06-30 No Support App Portal 2013 R2 2013-12-05 2016-12-31 2017-12-31 No Support App Portal 2013 2013-06-01 2016-06-30 2017-06-30 No Support App Portal 7.5 2012-12-01 2015-12-31 2016-12-31 No Support SCCM Expert 7.x 2012-12-31 2012-12-31 2012-12-31 No Support     The date format used is YYYY-MM-DD Versions not listed should be assumed as past extended lifecycle   Read a complete description of the   Flexera lifecycle and end-of-life policy  
View full article
A Cross-site scripting (XSS) vulnerability in App Portal 2018 R1 and earlier allows remote attackers to inject arbitrary web script or HTML via the note context parameter.
View full article
This article includes a PDF of a feature matrix for App Portal / App Broker that lists features and the deployment technologies and ITSM systems that those features support.
View full article
A SQL injection vulnerability in App Broker 2018R1 and earlier allows local users to execute arbitrary SQL commands via the MachineName parameter. 
View full article
Summary While attempting to integrate ServiceNow and App Broker an error occurs related to permissions in ServiceNow. Symptoms While attempting to perform any of the integration steps between App Broker and ServiceNow an error occurs. With verbose logging enabled the ServiceNowIntegration.log shows: Error while performing ITSM operations Exception has been thrown by the target of an invocation. com.glide.processors.soap.SOAPProcessingException: Insufficient rights for creating new records at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at AppPortal.Business.WebServiceInvoker.InvokeMethodAndReturnObject(String method, Object[] parameters, Int32 requestid) Cause This issue is most commonly seen in the following scenarios: The ServiceNow User Account defined in the ServiceNow Integration Page of App Broker does not have the required roles. The ServiceNow User Account defined in the ServiceNow Integration Page of App Broker has been changed to a new user that has the required roles. Resolution Please see the related KBs and documentation below for a resolution to each scenario above. Configuring a ServiceNow User Account for Integration with App Broker Changing the ServiceNow Integration User Account Credentials Additional Information Using App Broker for ServiceNow Creating a ServiceNow Integration User
View full article
Summary No response received during creation of catalog during sync between App Broker and ServiceNow. Symptoms When attempting to sync the App Broker catalog with ServiceNow you do not see any App Broker catalog items appear within ServiceNow. With verbose logging enabled the ServiceNowIntegration.Log may contain something similar to the below: Failed to update the catalog, Catalog details:8(Google Chrome (x64) 57.0.2987.1333) No response recieved during creation of catalog in ServiceNow.. at AppPortal.Infrastructure.Services.ServiceNowService.CreateServiceNowCatalog(Int32 packageId, String variableSetId) at AppPortal.Infrastructure.Services.ServiceNowService.SyncCatalogsInToServiceNow() Cause This issue is related to a ServiceNow setting which either permits or denies SOAP Responses which are not qualified. The setting can be located in ServiceNow by navigating to Web Servers > Web Services as shown below: The issue is currently being tracked by Flexera's Development Team under issue #IOJ-1883927. Resolution To resolve this issue the checkbox shown in the screenshot above can be deselected and then perform a restart of the ESD Service on the App Broker Server. However in some environments there may be other applications which rely on this setting remaining checked. If you are not able to un-check this setting you can proceed with the work-around below. Workaround If you are unable to deselect the check box noted above then a HotFix will be required. The only versions of App Broker which the HotFix can be applied to are App Broker 2017 R2 SP1 and 2018 R1. In order to apply the HotFix download the zip file from the attachments section of this article. The zip file contains two sub-folders, 2018R1 and 2017R2SP1, which contain the patched files for their respective versions. Back up the following files at each location below based on the version of App Broker you are using: AppPortal.Business.dll (2018R1 and 2017 R2 SP1) AppPortal.Infrastructure.Repositories.dll (2018R1 only) AppPortal.Infrastructure.Services.dll (2018R1 only) HtmlAgilityPack.dll (2018R1 only) ...\Flexera Software\App Portal\APM\bin ...Flexera Software\App Portal\Service ...\Flexera Software\App Portal\Web\bin ...\Flexera Software\App Portal\Utilities\MyApps Then proceed with the steps below: Stop the ESD Service on the App Broker Server. Extract the contents of the zip file to a staging directory. Copy the patched files for the desired version to the App Broker installation directory. Start the ESD Service. Launch the admin page of the App Broker Site. Navigate to Site Management > ITSM Integration Click on the 'Configuration' hyperlink for any ServiceNow system. Append the following to the end of the URL: &elementFormDefault=qualified Click Test and Save. Repeat steps 6-9 for each ServiceNow system in the ITSM Integration view. Additional Information Configuring SOAP Requests to Return Qualified Responses
View full article
Summary Information related to the required ServiceNow roles and permissions for a successful integration Synopsis In order for the App Broker and ServiceNow integration to succeed the ServiceNow User Account being used for the integration is required to have certain roles. Additionally, in order to provide the ability for end users in ServiceNow to request a catalog item imported from App Broker a specific role is required as well. Discussion Roles Required for Creating a ServiceNow Integration User: These are the minimum roles that are required for the ServiceNow User Account that will be used for the integration. x_fls_appportal.user catalog_admin mid_server web_service_admin pa_admin import_transformer Roles Required for ServiceNow Users: The below role is required in order for ServiceNow users to have the ability to request imported catalog items. x_fls_appportal.user Additional Information Using App Broker for ServiceNow Creating a ServiceNow Integration User
View full article
Summary When the App Broker catalog is synced with ServiceNow a variable set should be attached to each ServiceNow catalog item. If the variable set fails to attach during the sync then it can be added to the ServiceNow catalog items after the sync. Symptoms You have successfully synced the App Broker catalog with ServiceNow, but when examining the imported catalog items no Variable Set is associated as seen below: Cause It is expected that the App Portal Variable Set be attached to the ServiceNow catalog items during the catalog sync. This issue has only been seen intermittently as is being tracked internally by our Development Team under issue #IOJ-1903622. Resolution If the App Portal Variable Set is not attached to the catalog item during the sync then it can be added by a ServiceNow Administrator. The ServiceNow Administrator will need to modify the catalog items in order to associate them with the App Portal Variable Set. Additional Information Add a Variable Set to a ServiceNow Catalog Item
View full article
Summary This article should help you understand how the Licenses are accounted for in App Portal. It should also help you troubleshoot any out of Compliance alerts messages in your App Portal environment. Synopsis This article provides information about how User/Device based licenses are accounted for in App Portal. Discussion In App Portal, there are two types of Licenses which are present: User Type Device Type This information can be found from the License Entity field in the General settings under Site Management. For detailed understanding, please refer to the link below. http://helpnet.flexerasoftware.com/appportal2016/default.htm#helplibrary/APR_Settings_Gen.htm?Highlight=License type For User Based Licenses: By default, App Portal counts the number of users recently updated in the WD_User table within the App portal database using the following query: SELECT Count(UniqueName) from WD_User where lastupdate > DATEADD(day, -7, GETDATE()) and UniqueName is not null The WD_User table is populated during the nightly data sync with SCCM, and by default will include all users in the SCCM view v_r_user App Portal admins have full control over the license count, by specifying a "Custom User Sync SQL Query" (under settings->deployment->common). As an added benefit to user based licensing, a given user account should be able to have any number of device associations such that App Portal ends up using fewer licenses. The device where the user is accessing App Portal from, would not have to be a recognized by SCCM (mobile devices most commonly fall into this category). Switching to user based licensing is as simple as loading a new license file. For this License type, App Portal does not block a user from accessing the site, if the users are not recognized (not in vUser). The unrecognized user can access the site with the user name of "not defined". For Device Based Licenses: By default, App Portal will use the following query (run against the SCCM DB) to determine the license count: SELECT (COUNT(DISTINCT Name)) FROM v_FullCollectionMembership Where ResourceType = 5 AND IsActive = 1. If you wish to filter the above list, to reduce the number of licensed devices then you could use the settings that are found under admin->settings->web site. The licensed collection and License view setting allows you to select an SCCM collection or App Portal database View to base your device count on. For the Licensed Collection option, if you select " include" collection ", then only those devices that are in the specified collection will be included in the count. If you select " exclude collection ", then the count will be based on the above query, less the devices that are in the exclude collection .. Additional Information For User Based Licenses, to decrease the licenses used count, you would need to limit the number of users being imported from SCCM. This can be done by modifying the Custom User Sync Settings under settings-> deployment-> common. The Custom User Sync SQL Query can be modified to add a where clause or do a join with an existing user based collection.
View full article
Summary App Portal must be integrated with the Flexera Software Gateway in order to enable Enterprise Product Integration features Synopsis App Portal must be integrated with the Flexera Software Gateway in order to enable Enterprise Product Integration features. Discussion In order to take advantage of Enterprise Product Integration (EPI) features, it is necessary to integrate products with the Flexera Software Gateway (FSG). Integration for App Portal is done within the App Portal Admin view. In App Portal, open the Admin tab. Select Site Management > Settings. The General Tab of the Settings view opens. Open the Integration tab. In the Flexera Service Gateway Server Name field, enter the name of your Flexera Service Gateway server. Click Save. Other products integrated with the gateway will now be displayed below the server name. App Portal is now integrated to the FSG. Additional Information For the latest information on EPI configuration and troubleshooting, documentation can be found at http://helpnet.flexerasoftware.com/epi/
View full article
Summary Api's such as those found at: http:// /esd/api.asmx can be executed from Powershell. Synopsis This article discusses how to invoke an AppPortal API with Powershell. Discussion Api's such as those found at: http://<AppPortal Server>/esd/api.asmx can be executed from Powershell. For this example we will look at the following API: RemoveDeploymentForACatalogItem When clicking on that API from the api.asmx page there is a HTTP POST section displayed. In this section, parameters that it needs are displayed. For RemoveDeploymentForACatalogItem a "Title" parameter is needed. An example .ps1 script is: $username = "<domain\user>" $password = "<PASSWORD>" | ConvertTo-SecureString -asPlainText -Force $cred = New-Object System.Management.Automation.PSCredential($username,$password) $postParams = @{Title='<Catalog Item Title>'} Invoke-WebRequest -uri "http://localhost/esd/api.asmx/RemoveDeploymentForACatalogItem" -Method POST -Credential $cred -Body $postparams -ContentType 'application/x-www-form-urlencoded' $username, $password, and $postParams will need to be set (after the =) with your information.
View full article
Summary This article provides information on the fixes included in App Portal 11.0.3 (App Portal 2016 Service Pack 3) version. Synopsis This article provides information on the fixes included in App Portal 11.0.3 (App Portal 2016 Service Pack 3) version. Discussion App Portal 11.0.3 version includes the following fixes: App Portal 2016 Cumulative Service Pack 3 IOJ-1822979 - LastStatusID not set correctly for Task Sequences in DB IOJ-1824955 - App Portal does not enumerate AD groups correctly hence tabs not appearing correctly for users IOJ-1824959 - User/Device data sync error results in stop of sync process IOJ-1743586 - EULA notification does not support translation IOJ-1823376 - Having an apostrophe in the email address causes Single Sign-On mapping to fail IOJ-1823682 - Jobs Based Reclamation Process handles MyApps crashes when running the reclamation through task scheduler IOJ-1823474 - Catalog Categories view no longer appears after installing SP2 IOJ-1823626 - App Portal Does Not Support Re-Install of an AirWatch Mobile Catalog Item that has been Previously Installed (and Optionally Deleted) IOJ-1760343 - All icons, and red exclamation, displayed on My Requests page IOJ-1824684 - Searching Apps list from New Catalog Wizard not finding any results IOJ-1772747 - Reclamation alerts not created when more than one CI targets the same flexera ID IOJ-1772594 - Invalid column name error thrown in the MyApps_Exceptions.log file IOJ-1824960 - EULA does not display on the Browse Catalog page The latest App Portal 2016 Service pack can be downloaded by logging in to the Product and License Center.
View full article
Summary To enable App Portal API usage, the API must be turned on within the site's integration settings. Synopsis To enable App Portal API usage, the API must be turned on within the site's integration settings under Admin | Settings | Integration. Discussion In order to use the App Portal API, it must first be enabled within the site's configuration from Admin | Settings | Integration. Locate the "Enable App Portal API" checkbox and enable it before saving the page. If the API has been disabled, the following will be returned when attempting to invoke an API method: API Services are disabled Additional Information Integration settings
View full article
Summary Resolve the execute permission error being thrown. Symptoms In the databaseCalls_Error.log file the following exception may be seen: The EXECUTE permission was denied on the object 'fn_GetAppState', database 'CM_CAS', schema 'dbo'. The EXECUTE permission was denied on the object 'fnGetSiteNumber', database 'CM_CAS', schema 'dbo'. Cause This appears to be a database permissions issue on the SCCM database. Workaround To workaround this issue, add the App Portal service account to the smschm_users role on the SCCM database. The smschm_users role grants Execute permission to the SCCM database. Additional Information This issue is being tracked internally as Issue #IOA-000124115
View full article
Summary When attempting to access the App Portal Site, HTTP Error 500.19 is encountered Symptoms When attempting to access the App Portal Site, the following error may be displayed in the browser: Cause The Windows Authentication section is locked for the Default Web Site Resolution To unlock Windows Authentication at the Default Web Site level, 1. Using IIS manager, select Default Web Site under the Sites view 2. Under the Feature view, select Configuration Editor 3. In the Section field, select System.WebServer/Security/authentication/WindowsAuthentication 4. Select "Unlock Section"
View full article
Summary If administrator access to the admin site has been lost, for whatever reason, it is possible to set admin permissions back to the default settings. Symptoms If the message "You do not have access to this area" is displayed when trying to access the App Portal admin site, even though the logged in user has admin permissions, then it is possible that the permissions may have been corrupted or changed inadvertently. Cause This may occur due to user error, or possibly an issue with the data in the database. Resolution This type of issue can be resolved by resetting the admin permissions back to their default. Note that the default is that all users have admin permissions, so it will be necessary to reset the permissions.. To reset these permissions, run the following query: delete from WD_NodeSecurity After making this change to the database, perform an iisreset, and restart the browser.. Full administrator access should be restored for all users.
View full article
Summary Notifications can be customized to include the type of action selected in the request by using the standard variable ##Action## Synopsis Notifications can be customized to include the type of action selected in the request by using the standard variable ##Action## Discussion By default, some of the notifications indicate requests being submitted and executed successful, however these notifications do not differentiate whether the request action was an install or uninstall. These notifications can be customized to include the variable ##Action## within the message which would end up resolving to the type of request that was submitted. E.g. The ?Software - Install Successful" notification has the following wordings: "The installation of ##PackageTitle## has succeeded for the following computer:" The notification can be customized to: "The ##Action##ation of ##PackageTitle## has succeeded for the following computer:" Additional Information For additional information, see Managing Notification Email Templates and Messages
View full article
Summary This article provides information on the fixes and the link for App Portal 2015 R2 Service Pack B (10.0.2 version) Synopsis This article provides information on the fixes included in App Portal 2015 R2 Service Pack B (10.0.2 version) and the download link for that version. Discussion App Portal 10.0.2 version includes the following fixes: App Portal 2015 R2 Service Pack B IOJ-1745634 - Cross-Site Request Forgery in Web forms IOJ-1736414 - Input Validation IOJ-1736412 - Potential File Upload IOJ-1736411 - Cross-Site Request Forgery in MVC views IOJ-1736410 - Unencrypted Login Request IOJ-1736408 - Penetration Test and Vulnerability Assessment IOJ-1745077 - Catalog Items that are not enabled get displayed in the what's new and most popular section IOJ-1745467 - Default answers are not selected for Drop-down and Radio button answers IOJ-1744229 - Hide Sites from software publication setting not being saved IOJ-1744231 - Disable Approval for Leased Installations setting not working IOJ-1736413 - Session Identifier Expiration IOJ-1748660 - Collection Conditions for Altiris evaluated incorrectly The hotfix can be downloaded from the following link: App Portal 2015 R2 Service Pack B Additional Information The App Portal hotfixes and service packs are cumulative. Only the latest release would need to be installed. Current Available Hotfixes or Service Packs for App Portal 2015 R2 Version
View full article