ADFS HP RM Client authentication


In HP Records Manager 8.2 we added ADFS authentication as an option in the native windows client.  In this video I run through configuring this in our lab environment.

Things to copy and paste

Here are the various powershell commands I used on my ADFS server.

Create the ADFS client for HPRM.

Add-AdfsClient -Name "HPRM ADFS Client" -ClientId "ab762716-544d-4aeb-a526-687b73838a33" -RedirectUri "urn:ietf:wg:oauth:2.0:oob" -Description "OAuth 2.0 client for HPRM"

Set the token lifetime to force HP RM to check back with ADFS at defined intervals.

Set-AdfsRelyingPartyTrust -TargetName "My Relying Party Trust" -TokenLifetime 10

Tell ADFS to issue refresh tokens to all devices, you may also choose to specify WorkplaceJoinedDevices.

Set-AdfsRelyingPartyTrust -TargetName "My Relying Party Trust" -IssueOAuthRefreshTokensTo AllDevices

In the video I set the refresh token life in the UI but it can also be done with this powershell command. the maximum value ADFs will allow is 9999 minutes.

Set-AdfsProperties -SSOLifetime 480

Fun with 82 - Web service document cache

In this, the latest in my series on fun stuff in 82, I examine the new option for a larger web service document cache.

When is it operational?

This new setting affects the document cache used by the ServiceAPI, WebClient and WebDrawer allowing them all to cache a larger number of documents locally.  For the developers out there you can also take advantage of this simply by calling TrimApplication.SetAsWebService("c:\\SOME_PATH"); at the start of your web service.

WebDrawer 82 - Menu at top


The WebDrawer HTML is structured in a way that allows you to re-organise the page simply by applying some CSS.  In a previous post I looked at the custom_head.cshtml file which allows you to inject code into the head of the WebDrawer HTML pages.  In this post I demonstrate a technique to display the WebDrawer menu at the top of each page, rather than at the left.

Show me

The code

This is the code used in the video above


<link href="~/css/hide_menu.css" media="(min-width: 480px)" type="text/css" rel="stylesheet" />
<link href="~/css/top_menu.css" media="(min-width: 480px)" type="text/css" rel="stylesheet" />


#quick-search-forms > form:first-child +  hr,
#quick-search-forms > form:first-child +  hr + form,
ul.left-menu > li:first-child + li,
ul.left-menu > li:first-child +  li + li 

#leftcolumn {

#quick-search-forms {
    margin:0 10px 0 0;

#leftcolumn > ul.left-menu {

#quick-search-forms > form > button {
    padding:2px 0 2px 0;

#quick-search-forms > form > input {
    padding:2px 0 2px 23px;
    width: 170px;

#quick-search-forms > form:first-child {

Fun with 82 - Low impact CSS WebDrawer customisation


In HPRM 82 we introduce a simple new feature to allow you to inject your own code into the head portion of every WebDrawer page without changing any of the core templates.  This is done simply by adding the file custom_head.cshtml anywhere below your Views folder.

Watch it happen

The Code

This is the CSS I use to hide the Location quick search.

#quick-search-forms > form:first-child +  hr,
#quick-search-forms > form:first-child +  hr + form {

Fun with 82 - WebDrawer, search forms and IDOL

Fun with HPRM 82

Having spent quite a few hours reviewing, testing and playing with HPRM  82 I thought I would share some of my favourite things.  These are mostly technical things so you are unlikely to find me expounding on some great new records management feature, talk to support or sales for that.  This is the first in the series.

Searching in WebDrawer

A combination of some new features in HPRM 82 allow you to add something a little bit like a Google search to WebDrawer, all without writing any code.