Skip to main content
Solved

SF On Premise, End Product (runtime configuration) in Azure, how?


Forum|alt.badge.img+15

Currently we have the development environment on a local SQL Server Environment (On Premise). The product is targeting the Azure environment (Azure SQL database & App Service).

For testing purposes I want to be able to attach a project (branch) to an Azure SQL Database. Problem here is that it's kinda mixed mode: The SF-databases uses the Windows Active Directory (AD), whereas the Azure environment uses ‘rdbms’ users.

When I set up the ini file I sort of have the following:

metasource = sf
server = dev-server
database = software_factory
authentication = mswindows
project = branch
language = eng
rdbms = sqlserver
executionmode = developer

Problem here I use mswindows as authentication. But the Azure SQL Server uses ‘rdbms’.

I have a kind of a hack for it; I’ve added the same user/login to the on premise environment with matching name and password. That works, but I would prefer to use different credentials for the Azure environment.

Is there a way to do this? Or should I see if it's possible to bound the Azure environment to our local Active Directory? (https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication-configure?tabs=azure-powershell) (If it's possible, not sure)

Or in general, is this the way to do this?

Best answer by Jasper

The user interface probably expects another error message than the one returned by Azure. Can you please submit a ticket in TCP for this? Thanks.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

3 replies

Jasper
Superhero
  • 678 replies
  • February 7, 2020

Hi Rene,

If you log in to the Software Factory with Windows authentication and the same credentials cannot be used to log in to the end product, the (Windows) user interface should ask for an additional username and password. Does this not happen in your case?

 

 


Forum|alt.badge.img+15
  • Author
  • Superhero
  • 196 replies
  • February 7, 2020

Hi Guido,

In IAM, go to Users and set Allow change to true and set the Expiration policy to Forced expired. Next time the user signs in, the user will get a pop-up screen where the password has to be changed:

IAM - RDMBS force password change 

(Tested with Windows GUI)

Docs: Users · Thinkwise Docs (thinkwisesoftware.com)


Jasper
Superhero
  • 678 replies
  • Answer
  • February 7, 2020

The user interface probably expects another error message than the one returned by Azure. Can you please submit a ticket in TCP for this? Thanks.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings