E A I U S E R M A N U A L - Favv

More documents

Recommendations

Info

Web Service Security The Web Services are until now only secured using the XML web services user-account and password. And this account is shared by all XML users. Furthermore, we do not intend to introduce https for the web services, both for performance reasons and stability reasons. Especially in web services high-frequent https connectivity can cause problems. Additionally we do not expect people to strongly authenticate them using X509 certificates as this is probably overkill for this application... All XML users have to specify their User-account in the message. This account is used for treating the XML this sharing of the same connection is on itself not a problem. This user account is linked to the Party and Facility for whom the XML requests are being done (e.g. an arrival, a change notification,… ) and security and business rules are validated against this user account (Read: The XML is processed against the rights of this user). In addition, this user account is also used in the audit trail. Now, the attentive reader has detected two possible security issues. What if a hacker sniffs the message and resubmits it possibly with other information? What if you specify a user name you should not use? Let’s ignore the first one and focus on the second one... Indeed, theoretically people having access to XML messaging and knowing accounts of other users could submit an XML as if they were that user... That’s where the security token comes into play... In practice you still can leave the security token blank as this is a trusted user community. In addition you need to know the other user name and last but not least we do quiet some tracing on IP-address level to detect abuse or to do some analysis in case abuse is detected. This XML tracking also includes the content of the XML request so we actually can verify if XML users do not ‘abuse’ there XML capabilities by querying information they should not access... So no additional Web Service Security is for the time being still an option. Nevertheless we do invite you to implement one of the method-security elements discussed underneath. And as soon as you are on level 3 or 4 you also make the life of the hacker a lot more difficult... We now discuss how in the online application the XML security can be configured. This is done in tab 6 in the user profile.In this tab we manage some advanced security settings managing connectivity with the application both in the online as well as for the XML. The settings defined in this tab will define how you need to send your XML messages. Sanitel EAI Manual – v1.28 EAIManual.doc 124
Must Use SSL Logon Checkbox This flag indicates whether this User should logon via the Secure Server. If the user logs on via the normal login he is blocked for 2 minutes. We deliberately do NOT lock the user out because; - The password has been sent clear text over the line – so the ‘harm’ has been done anyway - the https channel might be cloased down as protection against from a standard https/virus attack Uses XML Checkbox The Uses XML checkbox is a flag that indicates that a certain LOGIN-account can also use XML to load / export information. Sanitel EAI Manual – v1.28 EAIManual.doc 125
Page 1 and 2:
E A I U S E R M A N U A L Version 1
Page 3 and 4:
1.10 Apr. 30, 2008 Extra Documentat
Page 5 and 6:
Table Of Contents Document History
Page 7 and 8:
Instructions to test the interfaces
Page 9 and 10:
Import S.20 IMRSN ImportTreatmentNo
Page 11 and 12:
Schema design conventions As there
Page 13 and 14:
Schema Definitions The attached zip
Page 15 and 16:
RIIT RiskItemType RIOG RiskOrigin R
Page 17 and 18:
GRP Group RCV Receive GSM GSM RDC R
Page 19 and 20:
GE18 18 Months or Older (SHP,GOAT,D
Page 21 and 22:
BF Buffalo (Bubalis bubalis) BIS Bi
Page 23 and 24:
HARE Hare RDT Rodent FURB Furbearer
Page 25 and 26:
HSPTL Animal Hospital PRCTC Animal
Page 27 and 28:
IPINJ IP injection TMT,BOV,SHP,GOAT
Page 29 and 30:
ULTR Ultra(Allflex Europe SAS) FL1A
Page 31 and 32:
RSPAD Responsible Party Address Cha
Page 33 and 34:
BLD Blood Analysis XMN Physical Exa
Page 35 and 36:
TUBR BlockingReason SANR Sanitary R
Page 37 and 38:
Sanitel EAI Manual - v1.28 EAIManua
Page 39 and 40:
Output Schema: AnimalExport http://
Page 41 and 42:
2004-01-20T00:00:00 2004-01-27T23:5
Page 43 and 44:
A query like this one can take some
Page 45 and 46:
Interface EXCNO - ExportChangeNotif
Page 47 and 48:
Interface EXFAO - ExportFacilityOve
Page 49 and 50:
Interface EXMNO - ExportMovementNot
Page 51 and 52:
Interface EXMVN - ExportMovementNot
Page 53 and 54:
Interface EXPAO - ExportPartyOvervi
Page 55 and 56:
Interface EXLPO - ExportLiableParty
Page 57 and 58:
Interface EXPUO - ExportProductionU
Page 59 and 60:
Interface EXPU - ExportProductionUn
Page 61 and 62:
Interface EXSU - ExportSanitaryUnit
Page 63 and 64:
Interface EXSUO - ExportSanitaryUni
Page 65 and 66:
Interface EXSLO - ExportSlaughterin
Page 67 and 68:
Example EXAGR3 - Who are the respon
Page 69 and 70:
Example EXMS-3 - Retrieve all Bovin
Page 71 and 72:
Output Schema: RetaggingNotificatio
Page 73 and 74: Output Schema: WaterManureAllocatio
Page 75 and 76: DST BE40006931 BE40006931-0101 B
Page 77 and 78: Interface IMCHN - ImportChangeNotif
Page 79 and 80: ANVS_CDE VRV Specifics ANVN_CDE Nam
Page 81 and 82: string string decimal Output Sc
Page 83 and 84: Interface IMMVN - ImportMovementNot
Page 85 and 86: ABC123 DLR BE102294097 TRA BE10
Page 87 and 88: DST BE03313736 BE118892877 Re
Page 89 and 90: string string decimal Example fo
Page 91 and 92: Interface IMPUN - ImportProductionU
Page 93 and 94: 10179333123 2 CHARLETS JOSEPH GRAN
Page 95 and 96: DGZ-V-HOM-M7-R-001 BE60666684 2 tr
Page 97 and 98: 1 4 1 4 Output Schema: Interacti
Page 99 and 100: BE87654321 BE87654321-0101 BOV G
Page 101 and 102: Direction: Import Purpose: Submit a
Page 103 and 104: {1} with value {2} ANIMAL,Country/
Page 105 and 106: Interface IMFCI- ImportFoodChainNot
Page 107 and 108: Import Food Chain Notification for
Page 109 and 110: Import Food Chain Notification for
Page 111 and 112: CMPC_CTRY_CDE_BAG string Pig 3rd Co
Page 113 and 114: Working On Behalf Of To support 3 r
Page 115 and 116: Channel 1. upload / download via se
Page 117 and 118: Another powerful feature of Web Ser
Page 119 and 120: Channels 2 to 4 The examples given
Page 121 and 122: Channel 4 - upload / download via w
Page 123: Production URLs All URLs specified
Page 127 and 128: The AES example is based on an EAS
Page 129 and 130: 8. Q: Can we put local animals and
Page 131 and 132: For “datetimes” this includes:
Page 133 and 134: So as output we return the animal n
Page 135: Support Online VIA the online bug /
show all

E A I U S E R M A N U A L - Favv

Create successful ePaper yourself

Delete template?

Save as template?