c# - Mobile application for Dynamics AX -
in our organisation trying develop mobile application/website front-end dynamics ax 2012. following architecture suggested microsoft (https://technet.microsoft.com/en-us/library/dn155874.aspx).
even though acs deprecated in azure architecture suggested microsoft forced use acs have created after requesting azure team.
dynamics ax architecture suggsted microsoft
steps followed per document:
we have setup following items , stuck @ 1 place:
setup 3 windows 2012 r2 servers running on single domain - first 1 ax & dc, second 1 adfs server, , third 1 middle tier wcf service - done & tested individually
setup of dynamics ax 2012 server aif service exposed in inboud ports - done setup adfs server , create few users - done, listening service bus according event logs & tested authentication using powershell console.
create sample console application call adfs token , pass azure service bus - adfs returning token , acs returning token
setup middle tier service sit in between ax 2012 & mobile client - setup done , service bus throwing 404 error
i have done steps , failing when trying contact service bus 2 tokens. have done before , know missing?
the post call service bus:
post url:
https://xxxxx.servicebus.windows.net/expenserest/expense?action=create headers:
content-type: application/json; charset=utf-8 authorization: wrap access_token="net.windows.servicebus.action=send&http%3a%2f%2fschemas.microsoft.com%2faccesscontrolservice%2f2010%2f07%2fclaims%2fidentityprovider=http%3a%2f%2ffqdn.com%2fadfs%2fservices%2ftrust&audience=http%3a%2f%2finvmobile.servicebus.windows.net%2f&expireson=1503321191&issuer=https%3a%2f%2fxxxxxxx-sb.accesscontrol.windows.net%2f&hmacsha256=ss%sss%ssss%3d&wrap_access_token" host: xxxxxx.servicebus.windows.net content-length: 4382 expect: 100-continue body:
{"adfstoken":"adfs_encoded_token","expensedata":{"amount":"100","comments":"expense of 100 inr","currenycode":"eur","date":"08/18/2017"} error:
404, no service hosted @ specified address
so if want use acs need white list feature via support request. new recommended way connect via sas. document refer above recommends building wcf service , or service bus listener .net code. there few diagrams refer particularly on page 27 or so.
so if work in .net code can implement sas right away more future looking trying make acs work.
some interesting additional data on sas, how implement it, ports open through firewall, etc.
ports need open depends on if use of clients or sb rest apis. documentation seems ports necessary: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-amqp-protocol-guide
azure service bus requires use of tls @ times. supports connections on tcp port 5671, whereby tcp connection first overlaid tls before entering amqp protocol handshake, , supports connections on tcp port 5672 whereby server offers mandatory upgrade of connection tls using amqp-prescribed model. amqp websockets binding creates tunnel on tcp port 443 equivalent amqp 5671 connections.
both modern clients should use amqp. there older client version unlikely used accenture: older .net library used @ point have custom, wcf based protocol used tcp on 9354 (called sbmp, sb messaging protocol) , @ time may have used older technology called webstreams
if use solely use our rest api might able use 443. little more data on sas https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas
wiki
Comments
Post a Comment