Skip to contentSkip to content
Spitfire Client Services

Spitfire Client Services

  • Support
    • KBA
    • Downloads
      • Implementation – Getting Started
      • Implementation – Templates
    • Training
  • Documentation
    • Focus Guides/TWP
    • What’s New in Spitfire
    • System Requirements
  • Newsletter Articles
  • Webinars
  • Video Library

KBA-01855: Bad Issuer Message When Logging In

Spitfire Client Services >> Knowledge Base>> KBA-01855: Bad Issuer Message When Logging In
June 17, 2024June 17, 2024| Soni YorkSoni York|
Categories:
  • Knowledge Base

Question:

I am trying to log into Spitfire. When I enter my ID and password and click the Log in button in Power UX, I get a “bad issuer” message. What should I do?

Answer:

V23, which default to the login screen in Power UX, requires secure URLs. The “bad issuer” message indicates that the URL is not secure. If you open Spitfire from a shortcut, that shortcut might have an older unsecure URL. You can know that the URL is not secure by the words in front of the URL:

Short Term:

Position your cursor at the beginning of the URL and type or ensure that it starts with https://

Long Term:

Change the URL on your shortcut so that it starts with https:// or talk to your IT expert.


KBA-01855; Last updated: June 24, 2024 at 10:25 am

Tags: login

Post navigation

PREVIOUS Previous post: KBA-01854: Pointing to RawItems in Bi-Directional Templates
NEXT Next post: Setting the Default Doc Status

Related Post

KBA-01358: Overview of the WBSConfig RulesKBA-01358: Overview of the WBSConfig Rules

Overview: The WBSConfig rules control various aspects of new Cost Codes added to Microsoft Dynamics SL. The WBSConfig rule group is found in the Rules Maintenance tool on the System

Read MoreRead More

KBA-01406: Alert LifespanKBA-01406: Alert Lifespan

Question: How long does an Alert stay in the system? Answer: A maximum of 62 days.  Of course, you can delete an Alert (or all Alerts) from your Home Dashboard

Read MoreRead More

KBA-01537: AP Check Format Change for Joint Checks from Spitfire Pay RequestsKBA-01537: AP Check Format Change for Joint Checks from Spitfire Pay Requests

Purpose & Scope: In order for the joint Pay function to work within Spitfire Subcontract Pay Requests, the AP Check format(s) needs to be adjusted in Microsoft Dynamics SL: Join the Project Controller

Read MoreRead More
  • KBA-01876: Using Workflow to Approve Docs Regardless of User Permission
  • KBA-01878: Releasing Retention on an SOV Pay Application
  • KBA-01877: Assembled PDF Output in Power UX
  • KBA-01874: Bulk Export from Catalog in Power UX
  • KBA-01875: Viewing Field History in Power UX
  • Client Webinars
  • Documentation
  • Knowledge Base
  • Newsletter Articles
  • Rules
  • Spitfire Reports
  • Training
  • Uncategorized
  • Videos (Power UX)
  • Videos (Quick, Basic Q&A)
  • What's New
  • Workflow Scripting

Meta

  • Log in

Spitfire Management, LLC
5219 Monticello Avenue #5444
Williamsburg, VA 23188

VW Machine Learning WordPress Theme Copyright 2025 Spitfire Management, LLC. All rights reserved.

Scroll Up