Jump to content

Search the Community

Showing results for tags 'login'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
    • GRC Manager
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start








Website URL





Found 6 results

  1. I am trying to locate the setting where we can update the text displayed when a customer experiences an error when attempting to login to the portal (Hornbill Direct Login). The reference to 'Hornbill administrator' means nothing to our external customers and is causing confusion. Is there a setting or translation option to edit this? Cheers Martyn
  2. We are currently working on a change that will slightly change the way that SSO works with Hornbill. Currently, when SSO (SAML) is configured, going to your instance endpoint, you will be transparently logged into the system once your iDP authenticates you and authorises your access to Hornbill you are automatically logged into the system. While this works fine, there are a number of cases where this behaviour is problematic. * If you have more than one SSO profile configured on your instance, getting back to be able to log in via a different SSO profile involves deleting a cookie on your browser. * If your iDP is not working, for example your SSO certificate has expired, you cannot currently log into the admin console without knowing a special URL parameter that you add onto the URL. This was a work-around which is error-prone and relies on technical knowledge which is not. In the future, Hornbill's underlying direct login behaviour will be changing to also use an iDP, so this work-around is no longer viable. * When you provide Hornbill support staff access to your instance, this is done with an API key, which is a work-around and will not be supported in the future, instead there will be some form of password/passcode scheme implemented which will allow you to give a Hornbill support member temporary access to your instance, where the Hornbill support team member will be able to visit the new login page and access an option to login with a temporary passcode. * There are other security enhancements we will be making in the future, such as 2FA and other pre-login notices etc, that some more security-conscious organisations require. * We are improving the way in which direct login works, especially around password reset, password expiry and password recovery. * There is currently a problem with browser sessions timing out, leaving tabs needing a refresh once you have logged in, we are looking at improving the overall session management functions around logging in, session timeouts and so on. The main change all Hornbill users will notice will be the appearance of a login screen, this will be shown, even if SSO is configured. If SSO is configured on your system a button labelled "LOGIN WITH SINGLE SIGN ON" will be shown (see screen shot below) and your users will need to press this in order to access Hornbill. As this is a change to the way it previously worked, we will also show a nano-training notice, pointing to the button giving a clear instruction as to what they should do to log in (i.e. press the button). you will also see this in the screen below, although the bubble is a moc-up, the real thing will be more classy that what is shown. If there is any problem logging in, or you need to log into the admin console to fix login issue with your SSO profiles, you can simply press the "HORNBILL DIRECT LOGIN" button and you will be presented with this screen. With this change in place, it paves the way for other security and login features will be added in the future. We expect these changes to be rolled out in the next 2-3 weeks. Thanks Gerry
  3. So today we are experiencing the issue in the image below on several peoples logins to various applications, there are also reports of slowness and 'cannot connect to database' errors.... is there something that is going on that we need to be aware of?
  4. If a users is in the customer portal and their session times out due to inactivity, they are returned to the main screen again when returning to the web page. However when they click on Login option to reconnect the Login process will report invalid session, when the correct and same user credentials are entered. It appears the timeout process does not cleanly browser session out properly and then causes issues when attempting log back in. Closing the browser and opening it a fresh then allows the user to log back in fine. This is causing some users to believe their accounts have been locked or their credentials are no longer correct. Can this be looked at to allow users to log back in cleanly after a session timeout. Cheers Martyn
  5. Related to my other post about Multi Language Landing Page for the Customer Portal, it would also be useful to have a multi language options on the Login Page as well. Once people are logged the portal will take into account their language setting but, we need to make it easy and native for them to get that far. Cheers Martyn
  6. Hi, Many of my colleagues and users / customers are reporting a strange behaviour on the service portal. When they click on the link that redirects then to our service portal (https://service.hornbill.com/XXX/servicemanager/request/view/SR00053013 for example), they get redirected to the login page. When they click on the login link, SSO kicks in and they authenticate ok. However, they then arrive on the landing page and many users do not even understand they need to go onto the "My Request" tab... Anyway, is this a new issue? Are you aware of a similar issue from other customers?
  • Create New...